- 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
Managing governed test case logs in the In Review state
Sign, void signatures, and comment on governed test case logs in the In Review state in Test Manager.
While a governed test case log is in the In Review state, it is immutable: it cannot be executed, and all editable fields on the log, including Create Defect, are disabled and show a tooltip explaining why. The current topic explains how to sign, void a signature, comment, and what happens if you try to execute a locked log or lock a log that is still executing.
Context
These are the operations you can perform on a governed test case log which has the In Review state.
- You can sign the log, declaring your role at the time of signature.
- You can void your signature.
- You can comment, with or without signing.
While the log is In Review, it is locked. This has the following effects:
- The log cannot be executed or re-executed.
- All editable fields on the test case log are locked, with a tooltip specific to test case logs, different from the tooltip shown for locked test cases.
- Create Defect is also locked, since a defect is an entity associated with the test case log.
- You cannot execute the log from a multi-select action, for example selecting multiple logs in a test set execution view and choosing Execute, if any of the selected logs is locked. Test Manager blocks the action with a tooltip and does not execute any of the selected items.
A test case log cannot change approval state while it is being executed. Test Manager blocks the action and shows an error. This applies the same way across manual execution, automated execution, re-execution, and override-result actions.
Signing a governed test case log
As an approver, you can sign a governed test case log that is in the In Review state to record your approval, declaring the role you held at the time of signature.
Steps
- Open a governed test case log you are assigned to as approver.
- Identify your name in the approvers' table and select the signing action.
- In the signing dialog, enter your role at the time of signature in the mandatory Your role at time of signature field. The field accepts free text up to 255 characters and shows a running character counter, for example "45 / 255".
- Select Sign. If the role field is left empty, the submission is blocked and the validation message "Please enter your role before signing." is shown, with the field highlighted as required.
Result
Your signature is saved together with your declared role, your identity, and the signature timestamp. Once submitted, the declared role cannot be edited. It is shown in the signature summary, for example: "Signed by Jane Doe as 'QA Lead' on 2026-04-28 14:32 UTC."
The role declared for a test case log's signature is independent of any role declared for the parent test case's own signature; they are separate signatory records. Records signed before this feature was introduced show the role as "Not provided."
Voiding a signature
You can void your existing signature on a governed test case log, reverting your approval status to Unsigned so the log can be re-signed if needed.
Context
Signatures can be voided by one of the following user types:
- The user who signed the record, if the record references the user directly.
- Any user in the group referenced by the record.
- Any user who has the Test Process Governance permission.
Steps
- Open the governed test case log.
- Go to the end of the row and select the Void signature icon.
- In the Add comment panel, enter a comment and select Save.
- Go back to the approvers' table. The Status column shows Unsigned against your name, and the signature timestamp is cleared.
To add a comment without signing, consult Managing comments for governed test case logs. Any user with the Test Process Governance permission, or with update permissions on the test case log, can comment, not only assigned approvers.
Result
The signature is voided and the Status column in the approvers' table is updated to Unsigned for your name. Once all required approvers sign, the log transitions automatically (implicitly) to Signed. Until then, it remains In Review and locked.