...
Step 2: Manual tests can be toggled to allow the status of a Scenario to be set independently for Jira Issue type including the “AssertThat Test Plan” issue type.
For Automated scenarios can also be managed independently by passing JQL with the execution results.
...
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 an “AssertThat Test Plan” from Scenario Manager
Scenarios can be easily selected and bulk added to create an “AssertThat Test Plan” in Scenario Manager
Step 1 : Access Scenario Manager
...
- Scenario manager is accessed from the feature page in AssertThat - BDD & Cucumber for Jira
...
Step 2: Filter the Scenarios using by Feature name, Scenario name, tags or any of the available filters. Then select the scenarios to add to the test plan
...
Step 3: Select Create Test Plan, and complete the Summary and Description details. When complete click on create
...
Note Scenarios can be linked to existing AssertThat Test plans using the existing linking functionality in Scenario Manager.
Mode, Linked to or tags on the Scenario Manager screen. Click on the “Filter” button to refresh the scenarios list.
Note the tags used for filtering can be either Scenario or Feature tags and advanced filter conditions can be used Use advanced search with Cucumber tag expressions in Scenario Manager
...
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: Complete AssertThat Test Plan Summary and Description and click on Create
...
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.
...
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.
...
Jira provides multiple options to link tickets. The scenarios will only be copied if the link type is clone.
Execute Scenarios and moving the AssertThat Test Plan to Done (lock Scenarios)
Step 1: Execute the Manual or Automated scenarios in the “AssertThat Test Plan”. Follow the same process you would to execute Manual or Automated scenarios.
...
Step 2: Lock execution status for the scenario by transitioning the ticket to “Done” status (Resolution = Resolved) using your existing workflows.
...
When the Test Plan is moved to Done:
...
The execution status of a scenario cannot be updated
...
It is not possible to unlink a scenario from the AssertThat Test Plan
Deleted scenarios can be removed from Features tab however will be highlighted as deleted
...