AssertThat Configuration & Enable for project

When you have installed the AssertThat - BDD & Cucumber for Jira application, you will need to enable it for your project.

Step 1: Navigate to the Project Settings and then select “AssertThat Integration”.  If you can't see the Project Settings option, the app will need to be enabled by your Project or Jira Admin.

Open

AssertThat Configuration page to set toggles and project setup

Step 2: Enable for project - Select Enable plugin for project.

Step 3: Scenario syntax validation - There are 2 further options to enable basic syntax validation for manual and automated tests.  As a minimum, we recommend you set syntax validation on for Automated tests. 

Step 4: Independent scenario execution - When enabled the manual scenario execution status can be managed independently for each user story. Further details can be found at Test Execution status for User Stories

Step 5: AssertThat Test Plan - used to manage, execute and report on tests grouped together, typically used for regression / release cycles. Details on configuring Jira issue types can be found here https://assertthat.atlassian.net/wiki/spaces/ABTM/pages/2234712139 . Further details on AssertThat Test Plans can be found here https://assertthat.atlassian.net/wiki/spaces/ABTM/pages/2234384385

Step 6: API access credentials - The Project ID, Access and Secret keys are required forhttps://assertthat.atlassian.net/wiki/spaces/ABTM/pages/728105165

Step 7: Automated Results filtering - when enabled the toggle filters automated results and only loads the scenario if it exists in the project. Further details can be found here By Default the toggle is set to disabled and the automated results will display “Scenario Missing” if the scenario doesn’t exist in the project.

Step 8: Scenario configuration

Step 9: Re-index issues- A full project re-index will re-synchronise AssertThat with Jira issue properties. Required on demand only.