Once testing is finished, you can mark a release execution or test run as complete. Completion locks the execution so its recorded results are preserved as a stable snapshot. If more work is needed later, you can resume the execution to re-enable edits.
Completion applies to both release executions and standalone test runs. The same controls are available from the execution overview.
When all testing is done, mark the execution as complete to lock it.
For test runs, the corresponding action is labelled Mark testrun as complete.
While an execution is complete, edits are blocked. Completion locks:
The execution remains fully viewable while locked, so you can still review results, analysis, and history. Completion only prevents changes; it does not remove any data.
If an execution needs further changes after it has been completed, you can resume it.
Resuming re-enables statuses, assignments, evidence, notes, and refreshes so testing can continue.
For a release execution, resuming depends on the state of its parent release. If the parent release is not in an executable state, the resume control is disabled and the execution stays locked. In that case, the release must return to an executable state before the execution can be resumed.
Test runs are standalone and do not have this restriction, so a completed test run can always be resumed.
You also need edit permission on the execution to mark it complete or to resume it.