Regression Tests
Regression Testing ensures that previously delivered features continue to work as new features are added. Teams build and manage an inventory of regression tests, create test plans for each new release, and manage testing activities within the sprint schedule.
Regression Tests are essentially templates for Acceptance Tests. They define the manual tests that are organized and executed as part of regression planning activities. Regression Tests can be created from scratch or generated from Acceptance Tests that are defined on completed backlog items. Every time a Regression Test is added to a Test Suite or Test Set, it creates an Acceptance Test, with the parent story or backlog item or defect being the Test Set.
The regression test grid can be organized using tags and then grouped into specific regression suites that will be used as templates to generate the executable acceptance tests on test sets. In this way, regression tests act as long-term templates for verifying previously delivered functionality that can be run repeatedly in the form of acceptance tests.
You cannot associate Tests with Backlog Groups. You can, however, associate them to a Test Set, as a parent Backlog Item for Regression Tests.
Who Uses Regression Tests
- Team Members: Create regression tests from acceptance tests after completing stories and defects, and execute regression test suites.
- Scrum Masters: Organize regression test inventory, manage regression planning activities, and track test execution progress.
- Product Owners: Review regression test coverage to ensure critical features are protected and approve which tests should be included in regression suites.
- QA Specialists: Build and maintain comprehensive regression test libraries, create test suites, and analyze test results.
Permission Requirement
To view regression tests, you must have Read access to the Product Planning area. To create, edit, or delete regression tests, you must have Edit access to the Product Planning area. To generate regression tests from acceptance tests, you must have Edit access to the parent backlog items or defects.
How Regression Tests Work
Template-Based Testing
Regression tests serve as reusable templates:
- Create: Define test steps, expected results, and acceptance criteria once
- Reuse: Generate executable acceptance tests from templates for each test cycle
- Organize: Group related tests into regression suites using tags
- Execute: Run tests repeatedly across releases to verify functionality
Relationship to Acceptance Tests
Regression tests and acceptance tests have a parent-child relationship:
- Regression Test: Template that defines the test procedure
- Acceptance Test: Executable instance generated from regression test template
- Test Set: Parent container (backlog item or defect) that holds acceptance tests
When you add a regression test to a test set, the system creates an acceptance test instance that inherits the test steps and criteria from the regression test template.
Troubleshooting
Why can't I associate a regression test with a backlog group?
Regression tests cannot be directly associated with backlog groups by design. Instead, associate regression tests to test sets, which are parent backlog items or defects. The parent backlog items can then be associated with backlog groups, providing indirect grouping of regression tests.
Why didn't my acceptance test update when I changed the regression test template?
Acceptance tests are snapshots created from regression test templates at the time of generation. Changes to regression test templates don't automatically update existing acceptance test instances. To use updated test procedures, generate new acceptance tests from the updated regression test template.
Why don't I see my regression tests when creating a test suite?
Verify that you're viewing the correct project scope in the Project Navigator. Regression tests are project-specific. If tests are in a different project or sub-project, adjust your project selection or move the regression tests to the appropriate project level.
Why can't I delete a regression test?
You must have Edit or Admin permissions to delete regression tests. If the regression test has been added to test suites or has generated acceptance tests, consider closing it instead of deleting to preserve test execution history and relationships.