Introducing TestFLO 7: Test Folders
Our team has recently been working on improving a test process area that our clients have identified as key to their success. Our clients’ feedback is valuable to us, so when we heard that test categorization could use some revamping, we set out to work!
Until now, users who wanted to categorize tests could take advantage of the built-in Jira mechanisms such as components or custom fields for this purpose. However, these methods weren’t sufficient because they only offered a flat structure. Also, the lack of a dedicated view makes working with tests more difficult.
TestFLO 7 solves the problem of test categorization by introducing a completely new module dedicated to this objective. You can find a brand new version of the app on the Atlassian Marketplace. Want to learn more about this useful feature? Read this article to see why test categorization is so easy now for teams that use Jira.
In TestFLO 7, test categorization is based on a tree structure of folders where users can organize Test Case Template issues. Each project that contains a Test Repository module running will be enriched with its test tree that can be modeled freely. The structure is multi-level, allowing for a more complex categorization in terms of attributes such as test type, module, version, tester, and many more. Also, each test can be placed in many folders within one tree. That way, users can create different categorization methods in the same project.
In addition to user-created folders, there are two default folders – All and Uncategorized. The first one contains all Test Case Template issues in the project, the second one only those that have not yet been assigned to any user folder.
Each folder in the tree contains information about the number of issues both directly inside it and all the issues with subfolders. This information allows users to easily evaluate the coverage with tests of a given category, e.g., a module in the product.
Laying out the folder structure for testing would have no value if we couldn’t use it in the test process. TestFLO 7 allows performing several popular operations from the folder level.
First of all, the user can create a new test directly in the folder, which significantly shortens the categorization time. After selecting this operation, the standard create issue dialog will open, and after the issue is created, it will automatically land in the previously selected folder.
Additionally, you can create a test plan based on a folder with all of its tests, but you can also add its contents to an existing test plan. With a properly designed test structure, you can conveniently prepare further test sets to execute.
The list on the right side of the screen shows the contents of the active folder. If this folder has more subfolders, the labels with paths leading to them appear in the list. Paths are not just informative but interactive. If you click on them, they take you to the appropriate folders.
The list of tests can be filtered using JQL queries. That’s extremely useful if your folders contain many issues. It’s often the case with the All folder where all tests are located. Thanks to JQL search, you can easily find the Test Case Template issues that you need and place them in the previously prepared structure.
The categorization itself consists of placing test issues in folders. This is done using the drag and drop operation that works between the list and folders, but also inside the list itself. In the second case, you can use it to move the tests between folders, but also to set the order in the single folder.
TestFLO 7 brings another essential element to test management in Jira. Test categorization based on a tree structure is flexible, comfortable, and, above all, functional. However, we’re already planning the next development phases of our test management app for Jira.
We’ll be working on new reports in the upcoming weeks. One of them will concern the performance of tests based on Test Case Template issues, while the other will allow analyzing and tracking defects with their priorities.
Another change we’re planning is the transfer of TestFLO Reports main functionality to the main app: namely, the export of test issues to PDF files. The same will happen to TestFLO Automation, which we also want to move and develop in the main app.
Stay tuned for more news about our Jira test management app, TestFLO!