In my last serie about building a testing framework à la xUnit left me with a weird feeling. Following Kent Beck's execution, from the book « Test Driven Development by Example », the exercise of thinking the Scheme way harder than I thought. I ended up with a shaky copy of the Python implementation. So I decided to let time passing by and come back to it to see what I can do differently. In the meantime, I watched a video of Andy Balaam where he showed a small illustration of the idea of Lambda Calculus and how it can be leveraged using a Scheme. That inspired me. Let's see how much, step by step…
The next item on the todo list: Report failed tests. The last chapter let the state of the test suite in a shaky state. Indeed, the last one is still red!
According to Kent Beck, the following chapter is like going one step deeper to deal with a more specific – smaller grained – as he said. To ensure our learning base (the tests) is rock solid!
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.
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 !