Skip to main content
System StatusContact Support
VersionOne Community

Regression Planning

Regression Planning is a Release Planning feature that allows you to define and map out coordinated sets of testing activities to ensure your existing functionality continues to work as designed. This is particularly critical for development projects in which new features are added.

A regression plan can contain multiple Regression Suites. Regression suites represent a set of related regression tests within a regression plan that, together, ensure proper functioning within a given aspect of the application. Teams can build and manage an inventory of regression tests, create test plans for each new release, and manage the testing activities within the course of the team's sprint/iteration schedule.

Regression Testing is an optional set of functionality that can be disabled or enabled through the Administration component.

Accessing Regression Planning

From the main menu, select Release Planning > Regression Planning.

Building a Regression Plan

Any one project or release can have multiple regression plans to organize testing activities. For example, you can create different plans for core functionality testing, new features, and performance testing. A plan can consist of a number of suites, each of which is made up of a number of individual regression tests. The regression suites act as templates for the test sets, which are generated to represent testing activities performed throughout the release. An owner may be assigned to a regression plan or suite to indicate the person responsible for coordinating its testing activities.

A single regression suite is typically executed under a number of different environments. The combination of a suite and an environment creates a test set, which is the asset you can schedule before or during sprint planning and execute its tests. The process of generating a test set creates an acceptance test for each assigned regression test under the suite. The acceptance test is the executable form of a regression test.

How Does Regression Planning Fit Into the Big Picture?

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).