Release Status Schema for Test Workbench Objects

As test organizer you can use this function to lock or release Test Workbench objects, such as test plans and test packages, to be changed or executed by the tester. The release status schema defines a set of release status values that you can set in the test plan.

Integration

You can use workflow as well as the release status schema. This means you can control and monitor the execution of tests more effectively. For example, the system tells testers when their test packages are ready for testing. For more information, see Workflow.

Features

Depending on the release status values settings in Customizing, you can influence the release of test plans and packages in the following ways:

Settable release status values
A status number is assigned to each release status value. The status numbers specify the release status values sequence in the release status schema. The system determines the settable release status values from the highest and lowest status numbers assigned to each release status value in the test plan attributes, and shows them in the input help.
Change lock
If a settable release status value is locked for changes in the test plan attributes, the attributes and structure of the test plan, including its test packages, cannot be changed.
Execution lock
If a settable release status value is locked for execution in the test plan attributes, a tester cannot execute his tests. He or she cannot change the test status.
Signature strategy
Note
A signature strategy is a combination of individual signatures required to sign a procedure. It specifies:
- Which individual signatures are required, that is, which user groups must sign the procedure
- In which order the individual signatures must be attained
- With which signature or signatures the signature process is complete
- Which signature method is used for signing, for example, user signature or system signature authorized by user ID and password.
End of the note.
If a signature strategy is assigned to the release status value set in the test plan attributes, these persons must sign to fulfill the signature strategy. If the signature strategy is fulfilled, the system sets the end status value. If the signature strategy is cancelled, the system sets the cancel status value.

You can assign signature strategies to the release status values. This only makes sense for statuses that have a defined end and cancellation status value, that is, review status in the standard release status schema.
BI-relevant flag
If this flag is set for a release status, the test plan data with this status is transferred to the BI system where it can be analyzed. For more information, see BI Reporting (for test plan status).

You can use one of the following release status schemas by default:

Default release status schemas (DEFAULT)

Status number	Release status	Initial status	Highest status number	Lowest status number	Change lock	Execution lock	End status of signature	Cancellation status of signature	BI-relevant
10	Test in preparation	X	20	20		X
20	Review for release		30	30	X	X	Released for test	Protected	X
30	Released for test		50	40	X				X
40	Review for adjustment (urgent)		60	60	X		Test in adjustment (urgent)	Released for test	X
50	Review for protection		70	70	X	X	Protected	Released for test	X
60	Test in adjustment (urgent)		30	30					X
70	Protected		80	80	X	X
80	Review for adjustment		90	90	X	X	Test in adjustment	Protected	X
90	Test in adjustment		20	20		X			X

Default release status schema simple (DEFAULTS)

Status number	Release status	Initial status	Highest status number	Lowest status number	Change lock	Execution lock	BI-relevant
10	Test in preparation	X	20	20		X
20	Released for test		30	40	X		X
30	Protected		50	50	X	X
40	Test in adjustment (urgent)		20	20			X
50	Test in adjustment		20	20		X	X

You can define your own release status values according to your own requirements. You can define your release status schemas and use the release status values of your status schema. For more information, see the SAP Solution Manager IMG under Configuration Scenario-Specific Settings .