Comments on: Bugs, Detectives, and Test Automation http://cwash.org/2008/03/11/bugs-detectives-and-test-automation/?utm_source=rss&utm_medium=rss&utm_campaign=bugs-detectives-and-test-automation += construction + craftsmanship; Fri, 26 Feb 2010 06:16:32 +0000 hourly 1 http://wordpress.org/?v=3.0.2 By: Chris Wash http://cwash.org/2008/03/11/bugs-detectives-and-test-automation/comment-page-1/#comment-3039 Chris Wash Thu, 15 Jan 2009 23:09:42 +0000 http://cwash.org/2008/03/11/bugs-detectives-and-test-automation/#comment-3039 Thanks for your comments, Inder. I agree, you should strive to have your test data as realistic as you can at the time, but you shouldn't worry so much about this to the point that it detracts from getting things done. Also, I agree that you'll want to prune your test suite, especially as requirements change. But I would never delete a test; rather, I'd move them into an "outdated" test folder. Sometimes requirements change back or you'd like to see how you went about testing a certain feature. If you delete them, they're hard to get back (maybe not impossible if you have things in SCM, but definitely a pain). This becomes less of an issue with newer frameworks like TestNG that support dependencies and grouping. You can group your out of dates and exclude them. Thanks for your comments, Inder. I agree, you should strive to have your test data as realistic as you can at the time, but you shouldn’t worry so much about this to the point that it detracts from getting things done.

Also, I agree that you’ll want to prune your test suite, especially as requirements change. But I would never delete a test; rather, I’d move them into an “outdated” test folder. Sometimes requirements change back or you’d like to see how you went about testing a certain feature. If you delete them, they’re hard to get back (maybe not impossible if you have things in SCM, but definitely a pain).

This becomes less of an issue with newer frameworks like TestNG that support dependencies and grouping. You can group your out of dates and exclude them.

]]> By: Inder P Singh http://cwash.org/2008/03/11/bugs-detectives-and-test-automation/comment-page-1/#comment-3038 Inder P Singh Thu, 15 Jan 2009 09:52:10 +0000 http://cwash.org/2008/03/11/bugs-detectives-and-test-automation/#comment-3038 I would like to make a couple of comments on the subject you have dealt with in your post: 1. The automated tests should include realistic test data. 2. Creating automated tests takes effort, which may prove helpful in avoiding bugs being introduced in code. However, the automated tests should be maintained to keep the automated test suite in shape (free from bloat). Old tests that no longer catch any bugs may be removed. Prior tests should be checked to see if they are indeed working as intended. If not, they should be updated. Inder P Singh I would like to make a couple of comments on the subject you have dealt with in your post:
1. The automated tests should include realistic test data.
2. Creating automated tests takes effort, which may prove helpful in avoiding bugs being introduced in code. However, the automated tests should be maintained to keep the automated test suite in shape (free from bloat). Old tests that no longer catch any bugs may be removed. Prior tests should be checked to see if they are indeed working as intended. If not, they should be updated.

Inder P Singh

]]>