In our new project, we've decided to use FitNesse with slilm. All in all, slim is an improvement over fit. The thing I like most is the error messages when running tests. These are now much clearer than with fit. The fixtures are now plain old objects (that's poo -- you can call them pojo, poco or even pono for all I care). So no dependency anymore on fit. Slim is also supposed to run faster, but right now our project is not really big enough to notice the difference. There's two things I don't like ......
Pfew... our presentation at the XpDays is done. You can find all the materials google code at this link: http://agileacceptancetesti... audience was great, and Pascal and I enjoyed it. We'll probably be trying to find something new to prepare for next year ......
Yippee, I will be speaking at the upcoming XP days in Mechelen. This is a first for me, and I'm really excited about this. Pascal Mestdach and myself have submitted a session on Agile Acceptance testing with FitNesse. It just got approved ......
After my previous post, I've got a FitNesse server running and configured. It's now time to write some tests. Of course, since this is a demo, this will be a simple, self-explanatory test. I'll implement a simple calculator, capable of adding two integers. Let's write that in FitNesse. First, I'll create a test suite called "DemoSuite". So I go to http://localhost:8888/DemoS... Since that page doesn't exist yet, FitNesse proposes a new page. I just accept it. Then I go to a subpage, that I call ......
What is FitNesse? Fitnesse is a tool that, if used wisely (big assumption), can turn requirements into functional tests. Examples can elaborate requirements. Examples can become tests. Tests can verify requirements. I'm not going to elaborate on the pro's and contra's of FitNesse. Others have done that before me. Installing the server Setting up FitNesse is a piece of cake. You just need to know the steps. First of all, go download fitnesse. Extract the downloaded content to a directory of your choosing. ......