This post is from the Collabnet VersionOne blog and has not been updated since the original publish date.
Reduce, Reuse, Recycle, Regress (ion Tests)
No, I’m not going to start singing the Sesame Street jingle, “One of these things is not like the other…One of these things just doesn’t belong”. When ‘Regress’ refers to regression tests in VersionOne, then surprisingly, the terms all represent the same concept. With regression tests, I can reduce my test planning time, recycle acceptance tests, and reuse regression tests. Taking the simple step to generate regression tests from acceptance tests gives you easy access to your test inventory, and tagging your regression tests turns them into a powerful test planning tool. By adding multiple tags to a single regression test, you can create regression plans and suites that will prevent dark, untested corners in your application. For example, take the asset link functionality in Roadmapping. The search aspect of this feature is built on top of the standard search functionality in the core application. To test this feature, I quickly found regression tests tagged for ‘Search’, and pulled them into a suite. Any tagged tests that weren’t applicable to the current feature under test were removed from the suite. Note the reduced test planning time! The resulting testset supplemented the acceptance tests on the story so that the team had a complete picture of the expected functionality. When the story was completed, I generated regression tests from the story acceptance tests, and added a Roadmapping tag to those tests. As promised, recycled acceptance tests! I also added a Roadmapping tag to the regression tests that made the final cut into the regression suite, so that the same tests will show up in either a Roadmapping tag search or a Search tag search. Regression tests are now primed for future reuse! Now you can be green too – reduce, reuse, recyle your tests!