 |
Articles Feed |
Categories
Archives
- July 2010 (5)
- June 2010 (4)
- April 2010 (3)
- March 2010 (2)
- February 2010 (2)
- January 2010 (1)
- December 2009 (1)
- October 2009 (2)
- September 2009 (2)
- August 2009 (1)
- July 2009 (5)
- June 2009 (2)
- May 2009 (2)
- April 2009 (8)
- March 2009 (7)
- January 2009 (2)
- December 2008 (3)
- November 2008 (5)
- October 2008 (4)
- September 2008 (6)
- August 2008 (4)
- July 2008 (5)
- June 2008 (5)
- May 2008 (4)
- April 2008 (2)
- February 2008 (4)
- January 2008 (2)
- December 2007 (2)
- November 2007 (2)
- October 2007 (2)
- September 2007 (1)
- August 2007 (3)
- July 2007 (1)
- June 2007 (4)
- May 2007 (7)
- April 2007 (2)
- February 2007 (3)
- January 2007 (3)
- November 2006 (3)
- October 2006 (3)
- September 2006 (17)
- November 2004 (1)
Three Reasons to Use FitNesse
by: micah | January 19th, 2007 |
1. You find your self delivering software to your customer who says “That’s not what I asked for.”
Using FitNesse allows you to communicate with the customer up front. Before a line of code is written, you can have all the behavior expressed in an executable format. Make sure the customer helps to write these tests. Once your FitNesse test is in place, all you need to do it make it pass. Due to the cut-and-dry aspect of executable specifications (FitNesse test), one the spec is passing, you have delivered precisely what your customer asked for.
2. Bugs sneak into your system as development progresses and these bugs takes weeks to find and remove.
FitNesse is a tools to help you drive development with tests. When practices with discipline, test driven development will insure that you have a FitNesse test for each and every feature in your system. The moment a bug is introduced, you will know about it because a FitNesse test will fail.
3. It is difficult to create documentation for your system and it is constantly out of date because the system is changing.
FitNesse offers a unique documentation solution. When ever you write a FitNesse test, you are in fact describing how the system works. In other words you’re documenting it. The web/wiki based nature of FitNesse makes documentation simple and convenient. The best part is that the documentation in FitNesse can never go out of date. Since you’re keeping your test passing, and your tests are documentation, it’s impossible for them to lie.
There is an article I wrote about FitNesse for Windows Developer Power Tools. This book, just released today, includes articles on dozens of free tools that .NET developers might benefit from. If you write .NET code, check it out. If not, keep in mind that FitNesse will work for almost any language.
October 18th, 2008 at 06:32 PM Thanks for participating in Tools Day, Micah! I just did a presentation on Fitnesse Friday at CodeMash (www.Codemash.org) and had several folks who were mightily impressed by the tool. Keep in mind that Windows Developer Power Tools isn't just for .NET developers! Yes, we've got a number of chapters dedicated to .NET-specific technology, but there's a great amount of tools and content which is platform-agnostic. All developers can benefit from learning about different source control systems, bug trackers, general Windows Utilities, SQL bits, security, etc. Thanks for writing a great article on Fitnesse for the book. I can honestly say that article is one of my favorites because I like that tool so much!
October 18th, 2008 at 06:32 PM nice article
October 18th, 2008 at 06:32 PM Hi Micah I am a manual tester and new to automation. I am trying to use this tool by reading about it. But either I am too lazy or not smart enough to figure out how to use it. Will you please give me detailed set of instructions abt how to test a simple application like Notepad using Fitnesse? Regards Bhakti