
In practice, what is the differnce between acceptance tests and regression tests assuming the same depth level and that the stories for which the acceptance tests were written have been accepted?
In a recent conversation with some of the team members regarding QA and testing terminology we explored the concept that acceptance tests for stories that have been accepted become regression tests in future releases. Then we wondered if this is true, then is there such a thing as a regression test or are there only sets of acceptance tests that grow from one release to another?
Is the term regression test then just a strategic term to describe the evaluation of acceptance tests not related to the current release but important to verify nonetheless?
Or are acceptance tests morphed into regression tests once the related story has been accepted, meaning the type classification is changed to regression?
Please let me know what you practice on your teams.
Thanks.
Comments
Generally you'll use acceptance tests to test new functionality you're building. Once the new functionality works, the acceptance tests can become regression tests to ensure that the new functionality continues to work. In Rally, you can put them into folders, schedule them for regression testing with test sets, and yes, change the type classification to regression if you like.
Reply to this Comment