Comments on: How to write a good test case: 5 tips to write better test cases http://www.makinggoodsoftware.com/2009/08/25/how-to-write-a-good-test-case5-tips-to-write-better-test-cases/ Thu, 29 Jul 2010 10:36:55 -0600 http://wordpress.org/?v=2.8.3 hourly 1 By: 8 Tips To Create Complete Test Cases | Test And Try http://www.makinggoodsoftware.com/2009/08/25/how-to-write-a-good-test-case5-tips-to-write-better-test-cases/comment-page-1/#comment-5239 8 Tips To Create Complete Test Cases | Test And Try Thu, 25 Feb 2010 08:14:55 +0000 http://www.makinggoodsoftware.com/?p=909#comment-5239 [...] How to write effective test cases How to write a good test case var fbShare = {url: [...] [...] How to write effective test cases How to write a good test case var fbShare = {url: [...]

]]> By: Are your unit tests on FIRE? | bigvisible.com http://www.makinggoodsoftware.com/2009/08/25/how-to-write-a-good-test-case5-tips-to-write-better-test-cases/comment-page-1/#comment-2005 Are your unit tests on FIRE? | bigvisible.com Thu, 19 Nov 2009 03:13:58 +0000 http://www.makinggoodsoftware.com/?p=909#comment-2005 [...] due respect to the author of FIRST but I prefer my version.) Trackback URL: [...] [...] due respect to the author of FIRST but I prefer my version.) Trackback URL: [...]

]]> By: Greg Young http://www.makinggoodsoftware.com/2009/08/25/how-to-write-a-good-test-case5-tips-to-write-better-test-cases/comment-page-1/#comment-944 Greg Young Mon, 31 Aug 2009 15:25:52 +0000 http://www.makinggoodsoftware.com/?p=909#comment-944 #1 in particular looks like a pretty naive pattern. There are good arguments on the other side of this discussion that in particular lead to specification style tests that offer better reading etc. With a specification I would move my code at the beginning of your method into a SetUp and then put each assertion into its own "Test" method. This in general can give me much more readable tests and I will tend to get more information when something fails (especially when multiple something fail because I don't need to run the test n times to know that). #1 in particular looks like a pretty naive pattern. There are good arguments on the other side of this discussion that in particular lead to specification style tests that offer better reading etc.

With a specification I would move my code at the beginning of your method into a SetUp and then put each assertion into its own “Test” method.

This in general can give me much more readable tests and I will tend to get more information when something fails (especially when multiple something fail because I don’t need to run the test n times to know that).

]]> By: Twitter Trackbacks for How to write a good test case: 5 tips to write better test cases | Making Good Software [makinggoodsoftware.com] on Topsy.com http://www.makinggoodsoftware.com/2009/08/25/how-to-write-a-good-test-case5-tips-to-write-better-test-cases/comment-page-1/#comment-888 Twitter Trackbacks for How to write a good test case: 5 tips to write better test cases | Making Good Software [makinggoodsoftware.com] on Topsy.com Wed, 26 Aug 2009 03:04:41 +0000 http://www.makinggoodsoftware.com/?p=909#comment-888 [...] How to write a good test case: 5 tips to write better test cases | Making Good Software www.makinggoodsoftware.com/2009/08/25/how-to-write-a-good-test-case5-tips-to-write-better-test-cases – view page – cached , 1.- Write a test case for every condition. There's a common misunderstanding- some developers translates one test case for every condition to one test case — From the page [...] [...] How to write a good test case: 5 tips to write better test cases | Making Good Software http://www.makinggoodsoftware.com/2009/08/25/how-to-write-a-good-test-case5-tips-to-write-better-test-cases – view page – cached , 1.- Write a test case for every condition. There's a common misunderstanding- some developers translates one test case for every condition to one test case — From the page [...]

]]> By: divclasshidden http://www.makinggoodsoftware.com/2009/08/25/how-to-write-a-good-test-case5-tips-to-write-better-test-cases/comment-page-1/#comment-887 divclasshidden Tue, 25 Aug 2009 22:50:40 +0000 http://www.makinggoodsoftware.com/?p=909#comment-887 "Test cases should be used as well as documentation on how your system works" Test cases should test how your system SHOULD work, not what it actually does. “Test cases should be used as well as documentation on how your system works”

Test cases should test how your system SHOULD work, not what it actually does.

]]> By: SD http://www.makinggoodsoftware.com/2009/08/25/how-to-write-a-good-test-case5-tips-to-write-better-test-cases/comment-page-1/#comment-886 SD Tue, 25 Aug 2009 17:21:04 +0000 http://www.makinggoodsoftware.com/?p=909#comment-886 It is simply fantastic information never seen before..thanks It is simply fantastic information never seen before..thanks

]]>