Show TOC

Procedure documentationOptimize Test Scope Locate this document in the navigation structure


The larger a change in your system is, the larger the number of business process hierarchy nodes affected. For example, when you import a support package, it often affects the entire business process hierarchy, which means the change impact analysis does not initially reduce the test scope.

A lot of affected objects are assigned to several business process hierarchy nodes, and are tested repeatedly. This function optimizes the test scope so that each object is tested at least once, but repeated tests are avoided. This can significantly reduce the test effort.

Note Note

The system optimizes the test scope under the assumption that an object has been completely tested when it has been tested at least once. So even if an object is used in several business processes, testing one node in the business process hierarchy is sufficient for the optimization strategy “test each object once only”. If you want to test some objects in their node contexts, you must exclude them from the optimization strategy.

End of the note.

To optimize, the system sorts all nodes in the business process hierarchy into an optimization sequence. They are sorted by test effectiveness. The test effectiveness is calculated from the relationship between the number of objects and the time required. The system uses either the total time required, or only the time required for manual tests, depending on the optimization options.

You can override the optimization sequence in various ways. The nodes are classified into the following areas, depending on the type of override:


Manually-selected nodes


Must include area: Nodes that must definitely be included in the test scope.


Preferred include area: Nodes that are marked as to be treated preferentially in the Business Process Hierarchy options


Not-overridden nodes (i.e. all nodes which are not in another area)


Must exclude area: Nodes that are excluded from the test scope

Areas 3-4 are also known as optimization areas.

The nodes are sorted by their test effectiveness within the areas. If you specify a test scope or the time available, nodes are put in the test scope or removed from it, by optimization sequence. The test scope always contains at least all nodes in areas 1 and 2, and at most all nodes in areas 1-4.


  1. Select a results data record from the Business Process Change Analyzer results list.

  2. Select the project or the solution to evaluate, in the top detail table (Result ID ...).

  3. Choose Optimize Test Scope.

    The coverage of the tested objects and the time required, are shown in a separate window.

  4. Specify the test scope according to your requirements. You can:

    Note Note

    The system takes your specification into account in the following sequence:

    1. Manually overridden nodes

      Nodes which you added manually are in the test scope.

      Nodes that you removed from the test scope manually are not include in the test scope (must exclude area).

    2. Business Process Hierarchy Options

      Nodes that were added to the must include area by means of a structure attribute are included in the test scope.

      Nodes that were added to the preferred include area by means of a structure attribute are only included in the test scope if this is permitted by the test scope and time resource values.

      Nodes that were added to the must include area by means of a structure attribute are included in the test scope.

    3. Criticality Options

      You can move modes to the must exclude area by deselecting the checkboxes for certain criticality options. A node is moved to the must exclude area if it contains objects up to a specific criticality only and is not already in the must exclude area as a result of a manual override or the Business Process Hierarchy options.

    4. Test scope

      Once the manual override and the Business Process Hierarchy options have been taken into account, your test coverage and time resource specifications determine the test scope.

    End of the note.
  5. You can use Create Test Plan to create a test plan for all test cases that exist for the affected executable entities (see Creating Test Plans for Projects).

  6. You can use Extend Test Plan to add test cases from the affected executable entities to an existing test plan. The system allows you to extend all test plans for the selected project or solution.