The next item on the todo list is Invoke tearDown afterward. But before doing this one, Kent wanted to take care of the order in which the procedures are called. This brings a new item : Log strings in WasRun.
So in this chapter we are going to implement a small logging system then the tearDown test fixture.
Have you ever wanted to hack on a free software project with a fellow hacker sitting next to you ? I did. But suddenly, I could not !
So I look for solutions to do remote pair-programming. I wanted to work on Guile projects, within Emacs, using Git, Autotools, etc. Do you know how many solutions are out there providing such environment to collectively hack in ? I've found none.
The next item on the todo list : Invoke setUp first
So here we will implement the test fixture usually called setup or beforeEach in other testing frameworks. It aims to execute code before any test function.
I love Test Driven Development. You might already know it if you are following my journey. Kent Beck wrote the book in 2002. He has chosen to provide examples using Java and Python in an Object Oriented way.
Now, I want to use the Guile programming language to follow the examples in the book and see how things are different !
Recently, I discovered WriteFreely.el, an Emacs extension to publish and update Org-mode files as posts on any WriteFreely instance (such as Write.as, as the default instance).