Release Status Schema

As test organizer, lock or release test objects, such as test plans and test packages, so that they can or cannot be changed or executed by testers. The release status schema defines a set of release status values that you can assign in the test plan.

You can use a 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.

Prerequisites

You have defined your release status schemas and use the release status values of your status schema in the customizing for SAP Solution Manager, under SAP Solution Manager Capabilities Test Suite Test Suite for SAP Solution Manager Preparation Setup Release Status Schema Set up Release Status Schema .
You have defined custom release status values according to your requirements in the customizing for SAP Solution Manager, under SAP Solution Manager Capabilities Test Suite Test Suite for SAP Solution Manager Preparation Setup Release Status Schema Specify Release Status Values .

Features

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

Selectable 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 selectable 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 selectable release status value is locked for changes in the test plan attributes, the attributes and structure of the test plan, including its attachments, test sequences, and test packages, cannot be changed.
Execution lock: If a selectable release status value is locked for execution in the test plan attributes, a tester cannot execute his tests and cannot change the test status.
Signature strategy: This is a combination of individual signatures required to sign a procedure. It specifies the following:
- 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.
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.

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*	Signature strategy ^**	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 ^*	Signature strategy ^**	End status of signature ^**	Cancellation status of signature ^**	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

^* X = checkbox is selected, and - = checkbox is not selected

^** - = input field is empty

Activities

You can assign the release status schema when you create a new test plan, on the Settings tab of the test plan editor. For more information, see Creating and Editing Test Plans. Here you also assign one of the supported release statuses.

Note Note

You can select a release status schema in the test plan attributes as long as the test plan has the status New. This is the case if the test plan does not have a test status yet and if it has no status schema or it has a status schema and the release status is still NEW.

End of the note.

If a signature strategy is assigned to the release status value, the system triggers the signature strategy automatically.

If execution of the current test plan release status is locked, the system displays the lock in the worklist of the tester of the corresponding test package.

You can now change the release status again and check the data in the change history at any time.