On this page

Test Plan Templates

Test Plan Templates can be used to define a list of all manual and automated tests, that should be run during a test cycle, as well as the configuration for which the selected tests should be executed. You can define many different Test Plan Templates, depending on the type of test cycle, so whether it is regular integration test cycle triggered by changes to the repository, or whether it is a potentially more in-depth testing cycle related to an upcoming release.

A Test Plan Template can be seen as a blueprint for a Test Plan Execution, which can be reused multiple times.

Test Plan Templates can be created within the Plan Templates tab inside the Tests view.

Test Plan Templates Tab

Search and filter Plan Templates

To search for a specific test plan template by its title use the field. Filtering test plan templates in the list by their tags can be done using the dropdown.

Plan Templates details view

After selecting a plan template, you can access and modify the details and configurations of this plan template in this view.

Test Plan Templates details view.

Renaming test plan templates

After creating a test plan template it will have a unique name by default, you can change it by clicking the button and the Rename Title dialog will pop up, enter the new title and press Ok.

Rename test plan template dialog

Editing test plan template description

You can set or update the description of your test plan template by editing the contents of the Description field. Simply click on the description field and enter the new description.

Test plan template tags

Tags can be assigned to test plan templates to simplify filtering and locating them in the Test Plan Templates tab. You can add multiple tags individually by editing the textbox

Group Planned Test Runs Table

You have the option to group the test plan runs table by using the dropdown. The following grouping options are available:

  • No Grouping displays the table in the default flat view.
  • Configurations groups the runs by their configuration.
  • Test Suites groups the runs by suite names.
  • Type groups the runs by execution type, either Manual or Automated.

Add Test Runs

You can add a new test run to a test plan by clicking on the + Test Run button in the Tests Plan Details view. This will take you to the Add Test Run view, where you select the tests and choose a run type. Test runs can be either Single — targeting one fixed configuration — or Matrix, which expands into multiple runs at scheduling time, one per label combination. For details on configuring matrix runs and setting up automatic user assignment, see Matrix Test Runs.

Suite Expansion

The Suite Expansion setting controls how the test run is populated with test cases once you have selected a suite. This setting is only available for automated test runs.

  • by existing test cases — Includes all test cases currently in Test Center for the selected suite. Use this to run the full set of known tests at the time of execution without manual selection.
  • from git repository — Test Center discovers test cases directly from the linked repository at execution time. This keeps the run in sync with the repository, automatically reflecting any updated tests.
  • no expansion - explicit — You select the test cases manually. The run contains exactly what you choose, and no automatic discovery takes place.

Note: Manual test runs always use no expansion - explicit — test cases must be selected manually.

Editing Test Runs

Test runs added to Test Plan Templates appear in the Planned Test Runs table, where you can still edit them by clicking directly on a row in the table, or by pressing the cog icon next to the Test Run you want edited. This will take you to the Edit Test Run view, where you will be able to edit the Assignee, the Labels and the tests of your selected test run. Press the Edit Test Run button when you're done editing.

Edit Test Run view

Matrix test runs are displayed differently in the table: each matrix run spans two rows, with the second row showing a sub-table of the configured label categories and their counts. The Labels and Assigned To columns are empty for matrix runs because these are resolved at scheduling time. To edit a matrix test run, click its row to reopen the configuration page. See Matrix test runs in the plan template for more details.

© 2024 The Qt Company Ltd. Documentation contributions included herein are the copyrights of their respective owners.
The documentation provided herein is licensed under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation.
Qt and respective logos are trademarks of The Qt Company Ltd. in Finland and/or other countries worldwide. All other trademarks are property of their respective owners.

Search Results