Skip to main content
System StatusContact Support
VersionOne Community

How Does Regression Planning Fit Into the Big Picture?

Overview

The graphic below shows the relationships between Regression Planning and other Release Planning assets (projects, regression suites, test sets, regression tests, acceptance tests, backlog items, sprints).

Process Flow

At a high level, the process is as follows:

  1. Deliver new backlog items  File:Import_with_Variables/Variables_v1/040/060/Feature-Icon.gif with acceptance tests File:Import_with_Variables/Variables_v1/040/060/Test-Icon.gif detailing the acceptance criteria.

  2. Generate new regression tests File:Import_with_Variables/Variables_v1/040/060/RegressionTest-Icon.gif from acceptance tests to allow continued testing of this new functionality.

  3. Create a regression plan File:Import_with_Variables/Variables_v1/040/060/RegressionPlan-Icon.gif for a new release to ensure existing functionality continues to work.

  4. Create regression suites File:Import_with_Variables/Variables_v1/040/060/RegressionSuite-Icon.gif under the plan to organize the required testing.

  5. Associate each regression suite with a set of regression tests to detail the functionality to be confirmed.

  6. Pair regression suites with an environment File:Import_with_Variables/Variables_v1/040/060/Environment.gif to generate a test set File:Import_with_Variables/Variables_v1/040/060/TestSet-Icon.gif to be scheduled for execution within a given sprint; in the process, each regression test becomes an executable acceptance test.

  7. Schedule the test set for execution during sprint planning.

  8. Run the tests for the selected environment.

  9. Create new defects File:Import_with_Variables/Variables_v1/040/060/Defect-Icon.gif for any failed acceptance tests and re-run the test set after the defects have been fixed.

  10. As necessary, the regression suite is used to generate new test sets in future sprints (for the same or different environments).