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 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 you add Test Runs, 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. You can create a Release 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 Suites and 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.
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.
Create a Test Cycle
- In Test Execution, select a Project in the Navigation Panel.
- Select the New Test Cycle icon.
- The "Test Cycle" page displays. Enter a Name for the Test Cycle in the field currently occupied by "Untitled."
- 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.
- Select a Target Release/Build for your Test Cycle in the "Target Release/Build" menu.
Note: This menu is populated by already made Releases and Builds.
- Select Save.
Create Test Suites
A Test Suite can be regarded as the lowest level container to organize test runs. For more information on the Test Suite, refer to Objects in Test Execution. Test runs can be assigned and executed in bulk as well as individually (test run by test run).
Create a Test Suite
- In Test Execution, select the Project, Release or Test Cycle in which you want to create your new Test Suite. This is done in the Navigation Panel.
- Select the New Test Suite icon.
- The "Test Suite" page displays. Enter a Name for your new Test Suite in the field currently occupied by "Untitled."
Note: If your new Test Suite was created within a Release, the "Planned Start Date," "Planned End Date," and "Target Release/Build" fields are automatically populated based on information associated with that Release. The "Assigned To" and "Execution Type" fields are also already populated.
- In the "Description" field, enter information about the Test Suite.
- In the "Environment" menu, select the proper Environment.
HINT: To create custom fields or modify existing system fields, see the article: Field Settings.
- Select Save.
NEXT STEP: See the article Add Test Runs to Test Suite.