Skip to main content
System StatusContact Support
VersionOne Community

Working with Regression Planning

This feature is available in Ultimate edition only.

editions-u.png

Overview

Regression Plans (and Regression Suites) are designed to be used either at the product or release level. You use regression plans at the product level for development scheduled to execute over the course of a number of releases. Create regression plans at the release level to be used just within the context of a single release. These plans/suites are hidden when the release is closed.

Regression plans and suites can be created and updated by testers, team members, and higher-level project roles. Regression testing is an optional set of functionality that can be disabled or enabled through the Administration channel.

Accessing Regression Planning

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

Creating New Regression Plans

You create regression plans to define coordinated sets of testing activities to ensure that existing functionality works as designed. A regression plan can contain multiple regression suites. To create a new regression plan:

  1. Go to Release Planning > Regression Planning.

  2. Click New Plan to open the Regression Plan window.

  3. At the top, enter a title, then assign your plan to a project by selecting it from the Project drop-down list. Optionally, you can enter a detailed description, assign an Owner, and include Reference data.

  4. Click Save. The system adds your new regression plan to the list of plan types on the left, and assigns it a unique ID (RP-nnnnn).

Creating New Regression Suites

A regression suite is a set of related regression tests within a regression plan. The tests are coordinated to ensure proper functional behavior within a given segments of the application. To create a new regression suite:

  1. Go to Release Planning > Regression Planning.

  2. Select a Plan Type from the list on the left for which you want to create a regression suite.

  3. Click New Test Suite... to open the New Test Suite window.

  4. Enter a Title that describes the nature of your high-level test suite. Optionally, you can enter a detailed description, assign an Owner, include Reference data, enter an Estimate, and add a Change Comment.

  5. Click Save. The system adds your new regression suite to the list of plan types on the left, and assigns it a unique ID (RS-nnnnn).

Viewing and Updating Existing Regression Plans and Suites

The Regression Planning page gives you summary views of regression tests and suites, as well as the ability to drill down into detail views where you can make updates to them or associated assets (regression tests, test sets, links, and attachments).

Deleting a regression plan requires that it be empty. Deleting a regression suite requires that no test sets be associated with it. So, to delete you must first delete any test sets, then delete regression suites, then delete regression plans, strictly in that sequence.

To view and update regression plan and regression suite information:

  1. Go to Release Planning > Regression Planning.

  2. From the Plan Type list on the left, click on the plan or suite you want to view/update.

  3. The Summary window opens for the selected plan/suite. This view includes rollup data for the tests currently under each regression plan and suite. Suites also show all associated regression tests and test sets generated from the suite.

  4. Click Edit to open the Regression Plan/Suite page, or click on the plan/suite ID to open the Details page and click Show Relationships to view/edit any associated regression tests, test sets, links, or attachments. To delete a plan or suite, click Delete on the far right (see note above about deletion rules).

  5. If making updates, click Save.

Moving Regression Plans to Another Project

  1. Go to Release Planning > Regression Planning.

  2. From the Plan Type list on the left, click on the plan you want to move. The Summary window opens for the selected plan.

  3. Click Edit to open the Plan page.

  4. Open the Project drop-down list at the bottom and select the project to which you want to move the plan.

  5. Click Save. The system moves the regression plan and all associated regression suites, tests, test sets, links, and attachments to the new project.

Assigning and Unassigning Regression Tests

Regression tests are grouped under regression suites. You can assign new tests to a suite, or unassign existing tests. To assign/unassign regression tests to/from suites:

  1. Go to Release Planning > Regression Planning.

  2. From the Plan Type list on the left, click on the suite for which you want to add or remove regression tests. The Summary window opens for the selected suite.

  3. To assign a new regression test to the suite, click Assign Tests and select a test from the drop-down list, then click Assign to move it under the selected regression suite.

  4. To unassign an existing regression test, expand the Regression Test subsection by clicking on the plus sign (+). Select a test from the expanded list and click Unassign to remove it from the selected regression suite.

Generating Test Sets from Regression Suites

You can schedule (generate) test sets within sprints/iterations when initially creating (or later editing) the test set. Or you can schedule test sets during sprint planning. Tests sets are created by default within the same project as the regression plan. You can move test sets to another (e.g., lower level) project if appropriate for work tracking purposes.

  1. Go to Release Planning > Regression Planning.

  2. From the Plan Type list on the left, click on the suite for which you want to generate a test set. The Summary window opens for the selected suite.

  3. Go to the Test Set subsection and click on the plus sign (+) to see the test sets already scheduled (if any) for the selected suite.

  4. To schedule a new test set for the suite, click Generate. The Generate Test Set window opens.

  5. Enter a test set Title and select a Project to associate it with from the drop-down list. Optionally, you can also define Environment, Sprint/Iteration, Team, Backlog Group, and Portfolio Item for the test set.

  6. Click Save to save the test set, or click Save & New to save and add (generate) another test set. The system adds your new test set to the list and assigns it a unique ID (TS-nnnnn).

Managing Regression Tests

Use the Regression Tests page within Product Planning to create and organize regression tests for each product. Each sprint/iteration generates new regression tests in your inventory directly from acceptance tests on the newly-delivered functionality. You can also create regression tests directly to cover previously-delivered functionality.

Monitoring Testing Progress

Use the Test Trend report filtered to Test Sets to focus on the progression of regression testing results.

Data for test sets roll up into other common reports as well. Estimate values are included in project burndowns and velocity graphs; To Do information is included in sprint burndown graphs, and test results are included in the existing test trend report. To view data for regression testing alone, use the Workitem filter in views of the backlog and in reports to focus on the data generated from test sets.

With Enterprise Edition, custom reporting on Regression testing can also be created with Analytics.

Tagging Regression Tests

You can use tags to filter regression tests when assigning them to specific regression suites. Multiple tags can be defined for any item. When entering tags:

  • Use the [space bar] to separate tags

  • Press [Tab] to go to the next field

  • Special characters are allowed in tags, acting as term separators when using the tag filter, so 'role:mgr' is effectively the same as two tags of 'role' and 'mgr' from a tag filtering perspective. Note, however, that special characters might cause unexpected results within the Find field and Advanced Search.

Executing Tests

You can execute acceptance tests on test sets the same way you execute acceptance tests on stories and defects on common tracking pages:

  • Testboard

  • My Home

  • Detail Tracking

  • Was this article helpful?