Execution case
Overview
You can subscribe to these execution case events in your app:
ones:test:execution_case:createdones:test:execution_case:updatedones:test:execution_case:removedones:test:execution_case:source_changedones:test:execution_case:source_change_resolved
Event delivery is at least once. Use eventID to process callbacks idempotently.
Every event includes non-empty executionCaseID, planIssueID, and sourceCaseIssueID fields in eventData, so the execution case, test plan, and source test case can be located directly.
📄️ Create execution case
This event is emitted when a test case is added to a test plan and a new execution case is created. An existing execution case reused by an idempotent request does not trigger this event again.
📄️ Update execution case
This event is emitted after one or more writable fields of an execution case actually change. Submitting unchanged values does not emit an event. An overall execution result change derived from step results is included in the same event.
📄️ Remove execution case
This event is emitted when an execution case is removed from its test plan.
📄️ Source test case changed
This event is emitted for each eligible execution case when a new source test case version contains a relevant content change, even if the execution case's source change status remains unchanged.
📄️ Resolve execution case source change
This event is emitted when a source change is resolved by confirming that it does not affect the execution case or by synchronizing the latest source content.