Show TOC

Function documentationTest Plan Management

 

Test plans are the set of all test cases which you need for a specific test phase. They can comprise the following objects:

  • Manual test cases

  • Test configurations (eCATT, composite tests, and all registered third-party test tools)

  • Executables

With test plan management, you create test plans that are based on Solution Documentation. Each test plan is defined for a set of solution, branch, and view. In context of test plan management, the view is very important, as it allows reducing the scope of the test plan. Working with a default view is not recommended because it can easily increase the test volume and lead to performance issues.

In the test plan, you select the exact list of test cases that you want to cover in a test phase. For each test plan, you define test packages, which consist of a subset of all test cases of the test plan. To the test packages, testers are assigned on.

You can create and print a test report which contains, for example, the test case descriptions, messages and status, in the Goto menu.

You can define test sequences to sort the test cases, in order to ensure a step by step execution, with the ability to assign each step to a different user. For a better control of the test execution, you can set up a workflow that is based on a Release Status Schema.

Integration

Organize tests after you have created a solution. For more information, see Solution Documentation.

When you create a test plan for a given test phase, the default test plan structure is based on the structure of the solution documentation

Prerequisites

  • You have set up a test system landscape in the landscape management.

  • You have defined the solution, with a branch and a view.

  • To the set of solution, branch, and view, you have assigned the test cases and executables that you want to test.

Features

With test plan management, you can do the following:

  • In the Test Plan Management application, you can create, edit, display, and copy test plans.

    You can also delete test plans, but this is only recommended for dummy test plans, for example. Real test plans must not be deleted because they are a proof of correct testing procedures.

  • Launch reports for selected test plan (choose Go To):

    • Test package analysis

    • Test case analysis

    • Defect overview

    • Create test report

  • Access the history for a test plan (choose Start of the navigation path Go To Next navigation step Test Plan History End of the navigation path)

  • Add or delete a test plan from your list of favorites (choose Favorites)

  • For selected test plan, you can see the list of test packages and perform activities on the test packages themselves:

    • Create, create from test sequence, edit, display, and copy test packages

    • Delete one or several test packages

    • Lock or unlock assigned testers (affects all assigned testers of the test packages)

    • Navigate to the test package attachments

    • Launch reports for the selected test package (choose Goto - Test case analysis

    • Defect overview

    • Access the history for a test package (choose Start of the navigation path Go To Next navigation step Test Package History End of the navigation path)

  • For a selected test plan, you can see the list of test sequences and perform activities on the test sequences themselves:

    • Create, edit, display, and copy test sequences

    • Delete test sequences

Note Note

If a test execution has already started, a deletion of a test plan, a test sequence, or a test package will also delete all related information, such as the test status, test note, test results, and defects assignments.

End of the note.