AssertThat Configuration & Enable for project
- Glib
- Nick
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.
Server & Data Center versions
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. Further details on AssertThat Test Plans can be found hereAssertThat Test Plan
Enable Test Plan - Enable custom issue type “AssertThat Test Plan” for your project
Enable cloning - Sets the default behaviour to copy scenarios when AssertThat Test Plans are cloned.
Step 6: API access credentials - The Project ID, Access and Secret keys are required for Integration with Test Automation Frameworks.
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 Automated results filter toggle. 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
Default Gherkin keyword language - Select the language from the drop down. English, French, Spanish, Portuguese and German languages are currently available. Further languages are available on request please contact support@assertthat.com
Default mode for newly imported or created scenarios. This can be set to either Manual or Automated.
When importing features, either through the API or the App, the mode of the scenario can also be set using tags at either Feature or Scenario level. The tags recognised to set the mode are @Automated or @Manual. The order of precedence for setting the mode is as follows:
-Scenario tag
-Feature tag
-Default mode setting
Step 9: Re-index issues- A full project re-index will re-synchronise AssertThat with Jira issue properties. Required on demand only.
Step 10 - Restrict Deletion - When enabled only Jira and project admins can delete scenarios and features. This is independent to bulk delete of Scenarios in Scenario Manager which is restricted to Jira and Project Admins.