The AssertThat Test Plan allows you to manage, execute and report on tests grouped together. This can typically be used when developing regression tests for a change or release.
AssertThat BDD scenarios need to be linked to the new Jira custom issue type “AssertThat Test Plan”. The Issue Type is enabled in the AssertThat Config page.
When should I use the new “AssertThat Test Plan” Issue Type to link scenarios?
Teams link Scenarios to Jira User Stories using the AssertThat plugin to develop living documentation. Teams can then easily view user stories and gherkin scenarios all in the same screen. Users can execute the Scenarios manually within the User Story, and also view the Automated test status of scenarios by importing the Automated test results using our integrations and API’s.
Teams typically create Test Cycles at specific points in time as part of their release cadence. Test Cycles can be setup using the “AssertThat Test Plan” issue type. Scenarios are linked to the “AssertThat Test Plan” issue type and can be executed for both manual and automated cases.
When complete the “AssertThat Test Plan” can be moved to “Done” as part of your existing Jira workflow. At this point the actual status of the tests will be locked, providing a fixed reference point and status that can be referred to in the future.
Key differences when adding Features & Scenarios to “AssertThat Test Plan” vs any other Jira Issuetype:
Scenarios linked to “AssertThat Test Plan” are typically used to manage Test Cycles.
When the AssertThat Test Plan” is in a “Done” Status:
Status of Manual and Automated tests are locked (note new functionality to import Automated test results for scenarios linked to specific Jira Issues. More information on how to specify the User Stories to update for Automated scenarios can be found here)
Steps and scenario status are locked for all scenarios that have been executed.
New Test Plan reporting available under “Test Plans Report”.