Manual Test Execution
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.
Manual test execution
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: Select the execute button, and 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". In addition, when the status is updated Comments can be added and recorded:
Step 3: The history of the status change including steps executed, who updated the status, date, 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. Enable the status by clicking on the Open Test Status button
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 is toggled on:
When scenarios are linked to a new Jira Tickets, the execution status will be set to “No Run” and will not inherit the execution status from the old User Stories.
For newly automated tests, when a scenario is switched from manual to automated the execution status will be reset to “No Run”.
Where the scenario type (manual/automated) is updated the previous execution status will be adopted.
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.