Best practices to use the Structure.Testy plugin:
|Table of Contents|
Create some universal checklists
You might have sanity tests, usability checklists and other lists of tasks that you run through regardless of the release scope. In this case you’ll find that it’s easiest to create a single structure and do multiple uniquely-named test runs in it.
This is easy to do:
Create your hierarchical list of issues and a unique View for displaying columns
Add a test run with a unique name that describes the test version and environment.
Set the result of each test for each issue. You can apply the same result to an entire group of issues by setting that result in the group’s parent issue.
Planning tests for a release
Displaying test progress alongside development progress makes it easier to understand overall progress and plan releases.
Create a structure
Add a Filter Synchronizer to pull in development issues for the release:
- Add your test cases as sub-issues of the development issues. Test case issues can be of any type and from any project:
- Note that on the JIRA view issue page you can view the structure an issue is contained in: