Master and child test plan artifact relationships

The Quality Management application supports master and child relationships for test plan artifacts and their child test plan artifacts, which includes test cases, test case execution records (TCERs), and others. You can evaluate the master and child relationships for test plans by setting a report query parameter in development intelligence reports for the Quality Management application.
Note:

Master and child relationships are excluded from Execution Trend and Defects arrival and resolution reports.

When you select Yes in the Include Child/Master Test Plans parameter, the child plans are listed in Test Plan under their master plan, prefixed with ->, as shown in the following screen capture.

The image shows the Include Child/Master Test Plans parameter in a report query.

The default value for the Include Child/Master Test Plans parameter is set to No. You must set the value for the Include Child/Master Test Plans parameter to Yes in order for the report to recognize master and child relationships for test plan artifacts. When Include Child/Master Test Plans is set to Yes, reports count all the child plans' artifacts as part of the master plan.

In the Test Plan parameter, if you select a master plan, and do not select its child plans, the report automatically adds all associated child plans beside the selected test plan. If you select a master plan, and also select some of its child plans, only the selected master plan and child plans are used to generate report results. Finally, if you select only some child plans but you do not select the associated master plan, the report automatically adds the master plan to the report result as well.

For example, if you open the Execution Status using TCER Count (Live) report, set Include Child/Master Test Plans to No, and then select the master plan “Master Test Strategy” and three child plans in the Test Plan parameter list, you would get the following result.

The image shows the generated report with the Include Child/Master Test Plans set to "No."

However, if Include Child/Master Test Plans is set to Yes, and the test plan selections are the same as in the previous example, you would get the following report result.

The image shows a generated report with the Include Child/Master Test Plans parameter set to "Yes."

In the previous example, all the child plan artifacts are rolled up into the master plan.

Exceptions for Requirement reports

The Quality Management application provides capability to reconcile master and child plan requirements in the current release. Requirement reports also operate according to this capability when Include Child/Master Test Plans is set to Yes. If you select a master plan, the report calculates the stacked set of all the child plan requirements, and then calculates the intersection set between the requirements of the master plan and the stacked set of requirements of the child plans. Reports show coverage based on this intersection set rather than requirements associated with the master plan. If you select a child plan, the report calculates the intersection set between the requirements of the master plan and the requirements of the child plans, and shows coverage based on this intersection set rather than the requirements of the selected plans.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki