Create Test Cycles with AssertThat Test Plans (Cloud)
- Nick
Capture and plan Test Cycles with the AssertThat Test Plan IssueType. The new IssueType allows users to plan Test Cycles by adding Manual and Automated scenarios to the “AssertThat Test Plan” IssueType.
Setup and Toggles for AssertThat Test Plan
Step 1: AssertThat Test Plan functionality is enabled using a toggle in the AssertThat configuration Settings pages. Go to Project settings → AssertThat configuration and enable the toggle “AssertThat Test Plan”
Optional Configuration (recommended)
Scenarios can be linked to one or many Jira Issues and the execution status set independently. For Manual scenarios, the execution status can be set independently for all issue types including AssertThat Test Plans.
Step 2 (Optional recommended): Independent Manual scenario status - For manual scenarios this is enabled through the toggle detailed below:
Independent Automated Scenario Status - Automated test status can be set for all scenarios (living documentation) or independently.
To set the automated scenario status independently pass the JQL with Jira tickets details as part of the Upload Report API or integration - more information can be found here.
To update the status of all automated scenarios don’t pass JQL params in API or Integration.
Setup AssertThat Test plans
Scenarios can be added to AssertThat test plans through 4 separate approaches:
Method 1 - Jira IssueType “AssertThat Test Plan”
Step 1: Create a new Jira issue and select “AssertThat Test Plan” from the Issue Type drop-down
Step 2: Select or Add new scenarios to the “AssertThat Test Plan”. Follow the same process you would to link Scenarios to Jira tickets.
Method 2 - Create “AssertThat Test Plan” from the Scenario Manager
Scenarios can be easily selected and bulk added to create an “AssertThat Test Plan” in Scenario Manager
Step 1: Access Scenario Manager
Step 2: Filter the Scenarios using Feature name, Scenario name, tags or any of the available filters. Then select the scenarios to add to the test plan. Finally, select “Create test plan” button.
Step 3: Adjust the display records field if the filter covers multiple pages
Step 4: Select the scenarios for linking, either by selecting all scenarios or individual scenarios, and then select “Create Test Plan”
Step 5: The Create issue window will be displayed and fill in the required fields. When complete click on the Create button and the AssertThat issue will be created with the Scenarios linked.
You may need to click on the Acceptance Tests button to display the AssertThat fields and linked scenarios on the newly created Jira ticket:
Note Scenarios can be linked to existing AssertThat Test plans using the existing linking functionality in Scenario Manager.
Method 3 - Link Scenarios to an existing “AssertThat Test Plan” from the Features tab
Scenarios can be easily linked to existing AssertThat Test Plans from the within the Feature.
Step 1: Access the Features tab, and open the Feature by clicking on the Feature title.
Step 2: Link the Scenario to AssertThat Test Plan by typing in the Jira Issue key. When you start typing, the list of available Issue Keys will be displayed.
Method 4 - Cloning existing “AssertThat Test Plan” from Jira
The AssertThatTest Plan can be cloned like any other Jira issue type. When the AssertThatTest Plan is cloned, the Scenarios will be copied to the Cloned ticket. Note that if the manual and automated toggles are set, then the status will be set to “Not Run” otherwise they will be set the same as the cloned AssertThat Test Plan
Note that if the Independent manual scenario execution toggle is enabled, then the status will be set to “Not Run” otherwise they will be set the same as the cloned AssertThat Test Plan.
Jira provides multiple options to link tickets. The scenarios will only be copied if the link type is clone.
See Also
Execute and locking AssertThat Test Plan
Execution report for “AssertThat Test Plan” issue type