Improvement in test management – TestFLO 6.0 is here!
We’ve just completed another period of intensive work on TestFLO, and the result is a brand new version of our app! TestFLO 6.0 is now available on the Atlassian Marketplace. This is a big step for us. We’ve introduced entirely new functionalities that improve the testing process. TestFLO 6.0 also restores its compatibility with Jira 8.
In this article, we introduce the changes we’ve implemented in the new version of our app. Read on to find out what’s new in TestFLO 6.0.
Iterations: a new way of retesting
Performing the same tests in subsequent cycles (for example, after bug fixes) is a natural part of the testing process. Until now, TestFLO allowed implementing that by copying subsequent Test Plans or reusing the same Test Plan with the snapshot saving functionality. Unfortunately, both strategies have their drawbacks. The first one burdens Jira with a large number of issues, while the second one doesn’t allow the use of saved historical data for analysis. TestFLO 6.0 solves that problem.
Test Plans have gained a new functionality that allows creating another iteration of tests. Use it to save the state of Test Cases and create new executions on the basis of the selected strategy. We can test all Test Cases again, only those that failed, all with statuses other than ‘passed’ or choose Test Cases manually. All the iterations will be visible in a tab on the Test Plan. On the other hand the Test executions tab on the Test Case includes all executions in iterations.
The second action associated with iterations is resetting the current iteration. Sometimes we need to start a given test cycle once again. Since the saved iterations can’t be removed, we’ve introduced an operation that allows restoring all Test Cases performed in the current iteration to their initial state.
We’ve also introduced changes in the Test Plan view itself. Now the Test Information panel includes the number of the current iteration. We also have the option of filtering the contents of the Test Cases panel so we can see all Test Cases or only those executed within the current iteration. Changing the view will allow testers to focus on current tests or preview tests as a whole.
Test Plan Iterations Report
The saved iterations of Test Plans can be analyzed on the tabs of the Test Plan itself, as well as the individual Test Cases. These views allow seeing test execution in a specific context, as sometimes we need a broader perspective. To this end, we have prepared a new report – Test Plan Iterations Report. You can use it to analyze all iterations of one or multiple Test Plans using a transparent matrix view. We can see both statistics on individual iterations, as well as the Test Cases. By filtering the Test Plans using version or a saved JQL filter, we can conveniently choose the data of interest.
Operations related to iterations are sensitive because they create data in the form of subsequent executions of Test Cases collected in iterations which can’t be removed and can be used for later analysis. To control the management of operations in TestFLO better, we’ve created a permissions module where operations related to iterations land in the first place.
Permissions can be defined at the global level, which allows you to manage them in many projects at the same time. Sometimes, however, you may need for a selected project to be different than others, and the configuration allows it. The Permissions tab allows you to set permissions that will apply to that particular project.
Permissions for iteration-related operations are just the first step for the permissions module. In the future, we will expand it with subsequent operations related to TestFLO to build a coherent authority management module for the testing process.
Jira 8 compatibility
On February 11, 2019, Atlassian released Jira Software 8.0, which brought a lot of exciting changes but created the need to adapt TestFLO to these changes. We’ve put a lot of time and work to make the necessary adjustments and tested the entire app under the new version of Jira. Today, we’re happy that TestFLO is compatible with Jira Software 8.0 and our customers will be able to use it following the upgrade.
TestFLO 6.0 is another significant step in the development of our app. We’re happy with what we’ve managed to achieve so far, but we’ll keep on perfecting it to make TestFLO meet the requirements of test management processes even better. Our philosophy is simple – we follow what brings our customers the most value.
One of the most-anticipated TestFLO functionalities is the possibility of flexible categorization of objects and in particular Test Case Template issues. We decided to implement a configurable tree to manage these issues in the next major version. The test repository structure will become more transparent and allow for more convenient Test Plan design.
At the same time, we’ll work on smaller versions that will introduce further improvements in the daily use of TestFLO. We plan to improve the issue search dialog (for example, when creating Test Cases) and add a new PDF export functionality. We will also expand the reporting capabilities through built-in reports, custom fields, or JQL functions.
We’re now ready to begin the next chapter of our journey to make test management in Jira even more suited to your processes and requirements. Stay tuned!
Visit the Atlassian Marketplace to try out the latest version of TestFLO!