Enter your mobile number or email address below and we'll send you a link to download the free Kindle Reading App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your email address or mobile phone number.
Shop the new tech.book(store)
New! Introducing the tech.book(store), a hub for Software Developers and Architects, Networking Administrators, TPMs, and other technology professionals to find highly-rated and highly-relevant career resources. Shop books on programming and big data, or read this week's blog posts by authors and thought-leaders in the tech industry.
> Shop now
Gojko Adzics "Test Driven .NET Development with FitNesse" came as a surprise. I found it by accident, no recommendation, no review and an unknown publisher. But... a good topic and a good name. So I got myself a copy and started reading it.. without regret.
This is a book which explains FitNesse.NET and it does it pretty well. FitNesse is the wiki front-end for Fit, the test tool developed by Ward Cunningham. Fitnesse was developed by ObjectMentor. The standard Fitnesse is more Java focused, this book covers the .NET variant.
The book is divided in three parts. The first part is a short introduction to Fit, Fitnesse and TDD. Also it explains how to install Fitnesse. The second part is a case example which gradually increases the difficulty level of the written tests. The third part is "advanced topics" which covers testing via the web interface, testing databases and testing legacy code. The final chapter (my favorite) is about the implementation of Fitnesse (and Fit) itself.
This is one of these books which just does what it should do. It gradually covers FIT. Gives clear explanations and good code. Builds up gradually. On the other hand, the book itself doesn't contain much new ideas, it is basically an explanation of the usage of a tool: Fitnesse.
Drawbacks of the book. Not too much. For me, the biggest surprise was that the book didn't started with the wiki-form of the test. Most of the time it worked from the fixtures to the wiki-test instead of from the wiki-test to the fixture ... which, in my humble opinion, ... would be more consistent with TDD. In line with that, the book does not cover too much about the process around the writing tests (or examples)... but Gojko also knew that so he wrote a new book: "Bridging the Communication Gap".Read more ›
Was this review helpful to you?
Gojko Adzic is a strategic software delivery consultant who works with ambitious teams to improve the quality of their software products and processes. He specialises in agile and lean quality improvement, in particular agile testing, specification by example and behaviour driven development.
Gojko's book Specification by Example was awarded the #2 spot on the top 100 agile books for 2012 and won the Jolt Award for the best book of 2012. In 2011, he was voted by peers as the most influential agile testing professional, and his blog won the UK agile award for the best online publication in 2010.