Test Execution Hierarchy
In qTest Manager, you can build a hierarchy within Test Execution to plan future test execution activities. This process consists of:
- Creating releases
- Creating test cycles
- Creating test suites
- Adding test runs to the test suite
During test planning, you can use the various objects above to plan out and group tests that need to be run. For example, you may have a suite of tests for new features being developed, another suite for UAT testing, or another for storing all your automation testing. Once test runs are added, you can also assign testers to execute the runs.
NEXT STEPS: See the article Examples to Build Your qTest Repository
A release is a milestone during which time certain requirements must be developed and tested. A release can be created in the Test Plan which will automatically create a release in Test Execution. We recommend creating releases in the Test Plan to serve as high-level milestones for your project. Within each release, you can create test cycles and test suites to build a more nested hierarchy and group tests by different variables, such as team, sprint, environment, functional area, etc. For more information, see the article Create a Release in Test Plan.
Create Test Cycles
A test cycle is a container that shows a high-level summary of its underlying test runs, including the execution results of these tests and any defects found. Within a given release, you may need to execute many types of tests. For this reason, you may have more than one test cycle within the release or even multi-level Test Cycles, which will be beneficial for organizing and reporting.
- Test Cycle can be created under Root tree, Releases, or Test Cycles
- You can create multi-level Test Cycles.
HINT: Before creating a test cycle, make sure you have already established a release plan in the Test Plan module. Many users will have already done so in another tool like JIRA or Rally, so feel free to align you releases to match up with your Fix Versions or Sprints. For more information, see the articles Create a Release and Add Requirements to the Test Plan.
- To create a Test Cycle, select the Test Execution module.
- Select a release object from the tree in the left panel.
- Select the New Test Cycle icon, the first icon in the left panel.
- Enter a name for the test cycle at the top of the page. For example, enter ‘New Test Cycle’.
- In the Description field, enter a description for the test cycle. Fill in any additional information for this Cycle in the Properties tab of the Test Cycle. You can determine which fields are required and which ones are not via the Field Settings area of your project.
HINT: The Target Release/Build field is automatically populated with a specific Release of the Test Cycle is organized within a Release.
- Click Save to save your updates.
Create Test Suites
A test suite can be regarded as the lowest level container to organize test runs. Test suites provide more specific information about a given set of test executions. It is here that you add test runs and specify the version of the test case that will be executed. Test runs can be assigned and executed in bulk as well as individually (test run by test run).
To create a test suite within a particular test cycle, perform the following steps.
- Select the Test Execution module and select either the release or the test cycle you want to add a suite within.
- Click the New Test Suite icon (the second icon to the left).
- Enter a name for the test suite at the top of the page. Note that the Planned Start Date, Planned End Date, and Target Release/Build, fields are automatically populated on this page based on information entered on the Release page if the Test Suite belongs underneath a Release.
- The Assigned To and Execution Type fields are also automatically populated on the Test Suite page.
- In the Description field, enter information about the test suite. Input information into the other fields on the Test Suite.
HINT: To create custom fields or modify existing system fields, see the article: Field Settings.
- Click the Save button to save your updates.
NEXT STEP: See the article Add Test Runs to Test Suite.