Agile transformations have been a hot topic among CIO’s and business area managers. Most companies are already done with it (or almost done), but for some, arranging the software development process (SLDC etc.) with the Agile approach can be difficult. In this article, we’ll try to show how to set up Agile tests managed in Atlassian Jira.
Testing in Agile
When using Scrum we have a sequence of sprints. During the sprint, a certain number of functionalities to be performed are defined, most often written in the form of Stories. Those requirements are then implemented by the developers and tested so that on the Sprint Demo the team can receive ready and properly working functionalities.
Atlassian Jira doesn’t provide us with test management features out of the box, that’s why we have to use external plugins. In our example, we will of course use the QA Craft for Jira plugin, the best QA plugin for Jira 🙂
Adding tests to requirements
Let’s start with viewing every Story that has to be done in one sprint:
From the level of the selected Jira issue type – Story, we create the exact amount of test cases required to test functionality (at least one TC).
In the beginning, when we don’t have any test structure, we must set a first Test Plan and Test Suite. It will be easier to manage our tests if we have them sorted out in that way. More about that in the next article.
Each sprint can have an individual Test Suite. This approach will help us keep order in our test plan. In case of creating a new Test Case, we should select the appropriate Test Plan and Test Suite.
Here we can see a freshly added Test Case (QACSANDBOX-255), this Story has a couple of TC’s. From this view, we can also see test progress for this requirement.
After creating all the test cases in “Sprint” we analogically do the same for the next Sprints. This will leave us with a complete structure for our agile project.
Complex test structure for Agile project
Here is an example of the more complex test structure for Agile project. As we can see, we can have large numbers of TC’s in separate Sprints. QACraft loves big test structures 😉
Reporting from testing in a sprint
We have full access to metrics, coverage reports, test coverage, and dashboards with charts presenting the execution of test cases and reported bugs. All this data is available for suitable sprints (Test Suits). Below are some examples of views.
Regression tests
“What happens with the old sprints?” – You might ask.
You can create a Test Suite / Test Plan named “Regression Tests” and drag&drop old Test Cases. All test statistics are saved.
In summary
I hope this article has proved that testing in Agile projects in Jira environment can be done and it isn’t this difficult. It all comes down to setting standards of work.
If You found this material interesting, leave a comment and follow for more Tips&Tricks in Jira, especially with QA Craft for Jira. 🙂
