Automated Test Execution
- Nick
AssertThat - BDD & Cucumber for Jira displays the execution test status against each User Story (or any Jira issue type) for manual and automated tests. The manual test status for the scenario can be updated on the user story itself.
Automated Test Execution
AssertThat provides a number of options for integrating with Test Automation Frameworks. The typical workflow would be
Scenarios developed in AssertThat
Scenarios downloaded using APIs or Integrations into the Test Automation framework
Tests executed and results imported back into AssertThat
Following the import of the Test Automation results back into AssertThat the execution status for the scenarios will be updated for all Jira linked issues. Note it is possible to update specific and independent linked scenarios on import - see Manual Test Execution | Independent manual scenario execution status
For Scenario Outlines where multiple examples can be executed under the same scenario are currently counted as a single execution. This is in the roadmap to change so the executions are counted independently.
Independent automated scenario execution status
Automated tests linked to the story will have the status updated following Test Automation Integration
By default scenario status will be updated across all linked user stories
A JQL filter can be supplied as a parameter with upload report as part of the Integrations or API call, so that only scenarios linked to filtered issues will be updated. The below example of the API is given below and this feature is also available in all the Automation Integrations.
More documentation on API usage can be found inREST API for Jira Cloud | Uploading report and Test Automation Integration
Automated Results filtering
Test Automation will be loaded by default even if the scenario isn’t matched in the AssertThat Plugin. To filter and only load results for matched BDD Scenarios enable the Automated results filtering toggle in AssertThat configuration project settings.