Skip to content

Planning of test runs

Use test plans to create the templates for the test runs that are performed later by the testing users.

You should create the test plans so that the testing users can work through related areas together in one test run: e.g. if you are testing a software project, you could create different test plans for testing setup installation packages on different platforms, or you could create one test plan for each platform that covers all the different areas across one program version.

To create a test plan, follow these steps:

  1. In the main window, select the parent element in the structure view. This is either the "Tests" node or the respective test folder.
  2. Right-click the element.
  3. Select "New test plan" from the context menu. → The "Edit test plan" dialog window will open.
  4. Enter you desired values. Usually, you will only need to fill in the "Title" field.
  5. Confirm with "OK".

The test plan will then be created and will be shown in the main window of the structure view. Add the test cases and test units that you want to be tested to the test plan.

Follow these steps to do so:

  1. Select the test plan in the structure view of the main window.
  2. Right-click the test plan.
  3. Select "Add test units and cases" from the context menu. → The dialog window "Select test units and test cases" will open.
  4. Select the test units and test cases that you want to be tests.
  5. Confirm with "OK".

After this, the test units and test cases will be added to the test plan.

Note

You can add a test case multiple times and at a hierarchy different to that originally intended by the author of the test case. This can be done by selecting the desired parent element below the "Template" element of a test plan and by selecting "Add test units and cases" from the context menu that opens.

After this step, a testing user can run test runs for the test plan you created.

Note

You can add test units and test cases for test plans that have no test runs yet.

Targeted retesting

Use Targeted retesting in Windows and Web to create a new run containing tests that should be repeated after changes. Select a reference run and the target environment. The overview explains each recommendation, such as a changed requirement, changed test content, or missing comparison evidence.

To open the selection:

  • Windows: Right-click a test plan or an existing test run in the project tree and choose Targeted retesting. Review the reference run, target environment and target variants, then refresh the analysis when needed.
  • Web: Open a test run and choose Targeted retesting. Select the reference run and target environment, then choose Find retests.

Select the tests and choose Check selection. If required predecessors are added, review the expanded selection again. Continue to run creation to enter the start parameters. The same permissions are required as for creating a regular test run.

Review the selection and optionally include failed tests. Tests with mandatory dependencies on changed tests appear as further recommendations. Required predecessors are added to the execution selection; informational links do not automatically expand it. Add missing prerequisites to the test plan first, or deselect the affected target tests.

If the template is older than the test library, you can explicitly synchronize the template. Existing runs and their results remain unchanged. If you continue testing the old template, the recommendation concerning the newer library specification remains visible.

The new retest run contains the selected tests without carrying over successful results. Previous results remain in the reference run. Do not treat a small partial retest as a new complete reference: tests absent from that run are not covered by it.

Comparison limits

Older results may not have reliable evidence of the content that was tested. They are shown as missing comparison evidence, not as unchanged content. Recommendations use requirements and links maintained in the project. Source-code changes in your application are not detected automatically. Success in a different environment does not cover the selected environment.

For comparison of release evidence and a documented decision, see Release comparison and acceptance. A partial retest does not replace complete release evidence.