When it comes to test case management in Jira, you’ve got two options.
One: You can configure your Jira instance to support test case management. However, this way you won’t get valuable test-specific functionalities and you’ll be forced integrate Jira with testing frameworks via CI servers.
Naturally, both problems can be addressed with custom Jira plugins. But developing a plugin takes time, and organizations can’t spare any these days.
Two: You use a tool that helps you transform your Jira software into a practical test case management suite.
We developed TestFLO to address this need and help enterprises plan, design, run and analyze tests.
With TestFLO you can easily create a functional repository of test cases which are in line with your test conditions and coverage criteria. Once your test cases are ready, you can prepare smart automation scripts thanks to test harness.
Your test plans can be filled with both manual and automated test cases from your repository. TestFLO then allows running test cases within plans using the test procedure you defined earlier, all the while filling out your test log for future reference.
But that’s not everything.
TestFLO delivers a broad range of quality metrics in reports which you can show to managers, developers, and testers to let them know what is the current status of your testing process.
Everything from projects and stories to plans and cases will be visible there together with defects and requirements.
With TestFLO, it’s possible to measure and control the exit criteria for each project, helping organizations to continually evaluate their testing processes and adapt them to respond to particular needs.
How to Make the Most Out of TestFLO for Your Company
Now that you know why TestFLO is worth your attention, let’s see what the add-on can do for your organization’s test case management.
Here are some examples of use cases to show you the full spectrum of functionalists available in TestFLO.
Create New Test Case Templates
The foundation of TestFLO are two elements:
- Test Case Templates which are specifications of your tests;
- Test Cases which can be created from Test Case Templates.
Test Cases can be embedded within a particular test plan, and – contrary to Test Case Templates – they are executed, and the status of their execution is recorded.
Organize Your Test Cases
TestFLO allows to categorize Test Cases in a hierarchic manner easily.
To help users do that, we added a special field for connecting Test Case Templates to Requirements. You can see this field here.
This field can be placed in any issue type. Adding such field to your test case, you can simply call it “parent Test Case” and this way build your hierarchy. You can then search for test cases easily by referring to their parent or children types.
To streamline this process, TestFLO can be configured to display child Test Cases in your parent Test Case. Here’s what it would look like – check point 5.
Another strategy for building a hierarchy for your Test Cases is using a native Jira mechanism such as issue links.
To help users make sense of their test case organization, we plan to add a comprehensive tree-structure view of the entire Test Case hierarchy in the near future.
Manual or Automated Test Cases?
When it comes to differentiating between automated and non-automated test cases, the out-of-the-box TestFLO installation won’t really see the difference between the two.
But since your Test Cases are nothing else than regular Jira issues, you can easily add a new field to your “Test Case” issue type, pick a new name for it, and turn it into a drop-down list where users can select either “Automatic” or “Manual”.
You’ll need to have administrative rights in your Jira to be able to configure these custom fields. Have a look here to learn more about this creating custom fields in Jira.
Automate Your Tests
For starters, the technology of automated testing is limited by:
- the supported continuous integration servers which are Bamboo and Jenkins;
- the XML reports produced in testing which need to be compatible with maven-surefire – most technologies on the market can generate such reports, for example, Junit, Selenium, .NET NUnit.
If you’d like to schedule an automated Test Case from a given test plan you can do that in two ways:
- on the side of Jira using a specific configuration
- on the Continuous Integration (CI) server’s side
We created as an additional plugin called TestFLO Automation to help organizations benefit from Bamboo or Jenkins which in turn perform Junit, Selenium, or any other tests which generate standard XML results.
You can be sure that these results are sent back to Jira in the form of Test Cases created in the test plan you set up previously.
With TestFLO, you don’t need to create a Test Case that will be executed automatically but simply define a test plan that would trigger automatic tests on your CI server when its status changes.
Once your testing process is finished, Test Cases will appear in the test plan with their statuses set to passed or failed. If they fail, you’ll get a detailed message showing you why it happened.
You can execute automated tests directly from Jira as well. To do that, just change the status of your already configured test plan to “In Progress” (or other), and it will schedule automatic tests to run on your CI server.
TestFLO is a go-to tool for test case management on Jira.
It’s straightforward and functional, allowing users to prepare a Test Case once and execute it many times on platforms like Jenkins, Bamboo, and others.
The results of your automated tests from testing frameworks like Selenium or Unit will be imported into Jira, helping you to keep tabs on your testing process and track any defects.
Click here to enjoy TestFLO in a free trial, and you’ll see how it can impact your organization’s testing process.
I am pleased to share knowledge about methodology, best practices, and IT standards. I use my many years of experience every day to support companies in optimizing their internal processes and developing strategies. I believe that people are the essential element in every team, and the most effective teams are those that work according to jointly developed processes and use tools that release their potential. Personally a pragmatist, entrepreneur, and passionate developer of algorithms, interested in psychology and development.