I spent the first iteration investigating basic Ruby and the tools available for creating automated tests. I am nowhere near feeling confident in all aspects of the language or on all the intrinsics of the tools but I hopefully I have enough to get the story planned for the next iteration going.

Ruby has a unit test functionality as part of its standard library, which is nice. It is a dynamically typed language so there should be a few new ways to create test doubles other than the ways its done in languages like Java or C#. There are a few mocking frameworks (Test::Unit::Mock and Flex Mock seems to be the candidates to choose from) available but I haven’t looked at those in any detail yet.

I was glad to see that RubyFIT is available for creating acceptance tests in FIT or Fitnesse. I haven’t been able to find FitLibrary and especially DoFixture implemented for Ruby. There seem to be some work going on with FitLibrary for Ruby though. If anyone has any info on this, please let me know. I will try to get on without it for now.

So now the second iteration starts. It is time to tackle the first user story!