Properly organizing Test Execution is critical to your team’s success. The organization not only affects how testers will use qTest on a daily basis but also heavily influences reporting in Insights.
Test Execution Organization
Releases are either manually created in the qTest UI or pulled directly from Jira. Whether using the Jira Integration or UI, any created Releases in the Test Plan mirror those in Test Execution:
Test Cycles are containers you can nest under Releases. Think of them as a page break, or a way to identify the overall element that you’re testing:
In this example, we are using Cycles to define the type of testing we are doing: UAT, Regression, etc.
Another way to use Test Cycles is to indicate the Component, Feature, or what you’re testing during execution
Note: You can nest Cycles under other Cycles to create Sub-Cycles
Test Suites are containers that nest under Test Cycles. They are for more granular grouping of Test Runs. In this example, we are in the "User Testing" Test Cycle, and are looking at various Applications:
As long as you understand the hierarchy of objects in qTest, you can use the containers to accomplish any configuration needed:
Here are some examples:
Again, the takeaway here is the hierarchy. As long as you nest things appropriately, your users will be able to find what they are testing.
Folder Structure and Reporting in Insights
Keep in mind, the way you structure Test Execution also impacts how you report in Insights.
Insights allows you to drill down by Test Cycle, Module, (folder from Requirements/Test Design) or Release (Sprint or Fix Version from Jira).
Note: All filters applied are persistent, meaning they will remain active until removed by a user.