Test Execution status for User Stories (Server and Data Center)

AssertThat - BDD & Cucumber for Jira displays the execution test status against each User Story (or any Jira issue type) for manual and automated tests.  Manual test status for the scenario can be updated on the user story itself. 

Set the test status for Manual test scenarios

Step 1: From within the user story, confirm that the test status is set to manual.  Please note the test status can only be set for manual tests:

Step 2:  Update the test status for the scenario when the manual test has been run.  The test status can be set to "Not Run", "Passed", "Failed", and "In Progress" as per the 4 scenarios below. In addition when the status is updated Comments can be added and recorded:

Step 5: The history of the status change including who updated the status, when and comments can be viewed by expanding “View execution history”

Step 4: The test status for the scenario is available to view on the user story. The status reflects the status of both automated and manual test scenarios. 

Independent manual scenario execution status

The toggle allows the status of a Scenario to be set independently for each User Story in Jira.

This functionality can be toggled on and off from the AssertThat Configuration page:

Points of note when Independent manual scenario execution status toggled on:

  1. When scenarios are linked to a new User Stories, the execution status will be set to “No Run” and will not inherit the execution status from the old User Stories.

  2. For newly automated tests, when a scenario is switched from manual to automated the execution status will be reset to “No Run”.

  3. Where the scenario type (manual/automated) is updated the previous execution status will be adopted.

  4. When scenarios are linked and unlinked to the same User Story, the execution status will be set to the previous value.

A video overview of “Independent manual scenario execution status” can be found here.

Independent automated scenario execution status

Automated tests linked to the story will have the status updated following Integration with Test Automation Frameworks.

By default scenarios status will be updated across all user stories.

JQL filter can be supplied as a parameter with upload report API call, so that only scenarios linked to filtered issues will be updated.

More documentation on API usage can be found in https://assertthat.atlassian.net/wiki/spaces/ABTM/pages/728105165 and https://assertthat.atlassian.net/wiki/spaces/ABTM/pages/766738433