- Getting started
- Project management
- Documents
- Working with Change Impact Analysis
- Create test cases
- Assigning test cases to requirements
- Cloning test cases
- Exporting test cases
- Linking test cases in Studio to Test Manager
- Delete test cases
- Manual test cases
- Document test cases with Task Capture
- Parameters
- Playwright test case fields
- Enabling governance at project level
- Disabling governance at project level
- Enabling governance at test-case level
- Disabling governance at test-case level
- Enabling or disabling governance in bulk for test cases
- Enforcing signing order for governed test cases
- Managing approvers for governed test cases
- Managing governed test cases in the In Work state
- Managing governed test cases in the In Review state
- Managing governed objects in the Signed state
- Managing comments for governed test cases
- Viewing governance information for test case logs
- Managing approvers for governed test case logs
- Managing governed test case logs in the In Work state
- Managing governed test case logs in the In Review state
- Managing governed test case logs in the Signed state
- Managing comments for governed test case logs
- Enabling governance at test case log level
- Disabling governance at test case log level
- Applying filters and views
- Accessibility testing for Test Cloud
- Project operations and utilities
- Test Manager settings
- ALM tool integration
- API integration
- Coding Agents for Testing
- Troubleshooting
Enforcing signing order for governed test cases
Require approvers on a governed test case in Test Manager to sign in a defined sequence instead of any order, and limit voiding to the last signature.
By default, approvers can sign a governed test case in any order. You can instead require approvers to sign strictly in a defined sequence. When signing order is enforced, only the last signature can be voided. This setting applies to test cases only; it does not apply to test case logs, and a log does not inherit it from its parent test case. Even when a log's parent test case has Enforce signing order on, the log's own approvers can still sign in any order.
Context
The setting exists at two levels:
- Project level (Project Settings > Governance > Signing order): sets the default for newly created test cases. See Enabling governance at project level.
- Object level (the Governance tab of an individual test case, next to Actions): overrides the default for that test case. The steps below set the order at this level.
Prerequisites
To change the signing order, you must hold the Test Manager Administrator role, the Test Governance Administrator role, the Project Owner role, or be assigned the Test Process Governance permission.
Steps
- Open a governed test case and select the Governance tab.
- Toggle on Enforce signing order.
- Select Actions > Change order.
- On the Change signing order page, reorder the approvers into the sequence in which they must sign.
Result
Approvers on this test case must now sign strictly in the order set. An approver can sign only once every approver earlier in the order has signed. If it is not their turn yet, no signing action is shown for their row. Only the last signature can be voided, not the ones before it. See Managing governed test cases in the In Review state for the full signing procedure.