By Robert Leitch on December 10, 2014
The super-streamlined Testy extension for Structure makes light work of manual testing. Our very own Julia Atlygina was kind enough to demonstrate how it's done at jtalks.org where Testy is used with JIRA Agile for testing in a Scrum workflow.
Is your manual testing as simple as this? If not, get Testy.
In short, Testy is to manual testing as jet propulsion is to making things go faster. Setting up tests for a release takes just a few minutes, while recording and reviewing results is one of the simplest things you'll do this year.
If you're already using Structure to organise your JIRA issues, rejoice! All you have to do is add a test run column to any structure, and it immediately becomes a simple test checklist.
More detailed test cases can be added as sub-issues and, because it's Structure, you can further group your test cases hierarchically if necessary.
At jtalks.org, the QA team creates a new structure for testing each release and configures a filter synchronizer to populate it with development tasks from the current sprint.
Test cases for different projects are kept neatly organized in structures that act as repositories. Instead of creating new test cases for each release, the QA team simply reuses existing test case issues, which are added to release testing structures using JQL search or by copy and paste via the structure clipboard.
These predefined test cases are added to the structure as child issues below each development task. After that they simply create a new test run column, and... that's it. They're ready to start recording test results.
Testy statuses aren't connected in any way to the JIRA issue workflow, so starting a new test run is as simple as adding another column to the test plan structure board.
Add as many test runs as you like
Since the test case issues aren't altered in any way when Testy results are recorded against them, they can be reused indefinitely. This makes it easy to compare successive test runs or the results of simultaneous testing in different environments.
If you're using Zephyr for recording test steps, you'll probably enjoy Structure's issue details panel that lets you open the JIRA issue view with Zephyr test details without navigating away from the structure board.
Because why would you ever want to leave the structure board anyway
Or if you're looking at the JIRA issue page for a development task, the Structure widget can show you its associated test cases and their results across multiple test runs.
Feel free to take Testy for a spin on our public Structure demo where you can mess things up without getting shouted at.
In case you were wondering, the voice in the video is mine, not Julia's...