Details of Xsquash
1. The product owner will define needs by writing epics and user-stories in Jira. These agile elements can then be synchronized into Squash to be displayed as requirements.
You set the Jira perimeter to synchronize: all the issues from a project, the issues from the active sprint, only the user-stories issues or tasks issues etc. The issues then will be automatically synchronized.
If you work with sprints as part of a Scrum Jira project, your requirements will be sorted in sprint files in the Squash Requirements workspace.
2. Once the user-story is written, acceptance criteria will be directly set in Squash TM with a collaborative approach: tester and his technical knowledge can be used for requirement definition in order to provide maximum added value to the identified feature.
These scenarios can be automated to be executed at each sprint or at each new release in order to cover a large perimeter of non-regression tests.
You also can link classic test cases (with action/result) to the user-story in order to complete the perimeter you have to test, or to design end-to-end tests, for instance.
3. Once test cases (written with Gherkin language or with a classic "action/result") are designed and linked to synchronized requirements, product owner, scrum master and developers will be able to track design and execution progress for each Jira issue test related.
Summarized indicators are recovered into Jira, as well as the details of tests related to a Jira issue and details of their executions (test data, dataset, execution steps...).
4. During test execution, tester will be able to easily design execution plan. In the Squash Campaigns workspace, a wizard allows to identify every test to be executed in order to cover a Jira perimeter (one/several sprint(s)/release(s) or according to a JQL request).
All the automated tests will be automatically executed. For other kinds of test, you will be able to execute them manually regardless of their format (Gherkin or classic tests written with "action/résult"). Results and details of executions will be directly displayed in Jira to allow the product owner, the scrum master or the developers to track the software quality.
5. If a test failed, tester will be able to directly report an anomaly from Squash. It will be pre-polated with all the data from the execution process to allow to know how to easily repeat an anomaly and make discussions easier.
The anomaly will be linked to Squash test case and to the tested Jira issue.
This feature is not included in the Xsquash plugin, but in the TM_Bt.JIRA plugin.