/
Manual Test Execution

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:

image-20260419-200651.png
Execute manual tests on Issue View

Step 2:  Select the execute button to run the scenario

image-20260419-200742.png
Click the execute button to run the scenario

Step 3: Select Add Execution

image-20260419-201005.png
Add execution details

Step 4: Add execution details including

  • Comments

  • Link to existing defect

  • Add new defect

  • Status.

When execution details have been added click on “Submit Execution” .

image-20260419-201306.png
Capture execution details including comments and linked defects then save details

The test status can be set to "Not Run", "Passed", "Failed", and "In Progress".

Step 4: View executed steps from historical runs can be viewed by selecting View Steps:

image-20260419-201701.png
View steps used during previous executions

Step 5: The test status for the scenario is available to view on the user story. The execution status can be filtered using the Overall | Automated | Manual toggles.

image-20260419-201843.png

Scenarios Outlines

The process for executing scenario outlines is very similar to normal scenarios. The only difference is that is to select which example you are executing.

Step 1 - Click on Execute button on a scenario outline, and notice the additional column “Examples”

image-20260419-203841.png
Execute scenario outline

Step 2 - Click on Add execution and from the drop down select which example you want to execute

image-20260419-203948.png

 

Step 3 - Status and execution of examples. The drop down displays the execution status of the examples which is useful if there are a large number of examples in the scenario outline.

image-20260419-204235.png
Scenario example status

 

The overall status when there are multiple examples follows the below logic:

Example Status

Overall Scenario status

Example Status

Overall Scenario status

All scenarios Not Run

Not Run

One scenario In Progress or 1 scenario Passed and pending scenarios

In Progress

One example failed from multiple examples

Failed

All examples passed

Passed

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:

image-20260419-202109.png
Enable Independent scenario execution toggle to execute tests independently across multiple Jira tickets

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

  1. 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.

  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.