Execute Scenarios and moving the AssertThat Test Plan to Done (lock Scenarios)

Owned by Glib
Last updated: Apr 01, 2024 by Nick
2 min read

Step 1: Execute the Manual or Automated scenarios in the “AssertThat Test Plan”. Follow the same process you would to execute Manual or Automated scenarios.

Execute Scenarios on the AssertThat Test Plan Issue type

 

Step 2: Lock the execution status for the scenario by transitioning the ticket to “Done” status (Resolution = Resolved) using your existing workflows.

AssertThat Test Plan execution status is locked when the resolution state is Done

When the Test Plan is moved to a Resolved state:

  • The execution status of a scenario cannot be updated

  • It is not possible to unlink a scenario from the AssertThat Test Plan

  • When you download Features / Scenarios either through AssertThat or via the API, resolved Test Plan issue keys won’t be included as scenario tags.

  • Deleted scenarios can be removed from the Features tab however will be highlighted as deleted

See Also

Test Plans Report for “AssertThat Test Plan” issue type