Specifying the Test Scope or Time Resources

The test scope is the proportion of the objects which are in at least one tested node of the solution documentation. The time resource depends on the test cases which you have assigned to the nodes. The higher the coverage, the higher the time required, although you can often achieve nearly complete coverage (95 %, for example) with significantly less effort (half of the total effort, for example).

The Test Scope Definition display area shows a bar chart of the currently-selected test coverage, and the time required, divided by manual and automated test cases. The markings in the bar chart indicate the coverage and time required values which you can achieve by testing individual nodes. As the system only counts the total number of all objects and test cases at a node, only certain coverage and time required values are possible.

Prerequisites

You have specified the time required for your test cases. You have

entered the time required directly in each test case

entered default time resources for the various test case types.
For more information, see Maintaining Default Times for Creating and Executing Test Cases.

Procedure

Select the time unit and enter the required value in the Value field next to a bar (the Total Test Effort bar, for example), or click directly on the bar.
Confirm the entry with Enter.
The system calculates the next-highest test coverage, and its required time. The bar chart is automatically updated. On the Test Scope Optimization Ranking tab page, the test scope is indicated in the diagram under Graphical View by a light green background.
Note
If you do not achieve a test coverage of 100%, there are object in nodes without test cases, or you have excluded test cases via the optimization options, so that it is no longer possible to test all the changed objects in a node. The system does not initially include these nodes in the optimization, it queues them in the optimization sequence at the end of the optimization area. You can include these nodes in optimization as follows:
- Assign test cases to the nodes.
- Change the test case options so that the system can take other test cases into account.
- Put the transactions to be tested, in the test plan, as follows.
  Expand the Test Plan Generation Options.
  Select the Include transactions without test cases check box.
  Choose Apply and Save.
  The objects at the nodes without test cases are also testable, and are optimized by the system. When you generate a test plan, the system includes the transaction in the test plan. You can start the transaction from the test plan.
End of the note.