Execution Plan Editor - Test Item List Panel

Applies to TestComplete 15.0, last modified on October 14, 2021

The Test Items panel of the Execution Plan editor shows the project’s test items in the order they will be run.

The Test Item List panel

Click the image to enlarge it.

The editor looks like that by default. If you run your tests in sequence and prefer the main view of the editor (without the Parallel Device Cloud Environments panel), use the button in the right-top corner of the editor to hide information about parallel environments.

The Execution Plan editor

Click the image to enlarge it.

If a column with the desired test item’s property is hidden, to make it visible, right-click anywhere on the editor, click Field Chooser, and then drag the needed column from the resulting list to the page.

You can customize the column layout. For example, you can reorder or hide some columns. For more information, see Arranging Columns, Lines, and Panels.

A test item can be:

  • A keyword test
  • A script routine
  • A low-level procedure
  • A network suite, or its job or task
  • A BDD scenario or several scenarios
  • A unit test or a Selenium test
  • A ReadyAPI functional or security test
  • A tag or tag expression specifying one or several tests (keyword tests, script routines, and BDD scenarios) to run

You can organize test items into a plain list, grouped list, or a tree-like structure (where child items are run after the parent item has finished running) and change their properties. For example, you can exclude test items from or include them in the test run using the check box next to the test item name.

The following table contains descriptions of test item properties.

Test item properties are not applied to tests that are not launched as test items (for example, they are launched from the Project Explorer or are called from another test).

Column Description
Name The test item name.
Test case Marks the test item as a test case. This item will be included in the Summary report.
Notes
  • Individual BDD scenarios are always marked as test cases.

  • Scenario outlines are never marked as a test case. The way TestComplete treats outlines depends on the Treat each example in Scenario Outline as a separate test case project property:

    • If the setting is enabled, each scenario example of the outline will be treated as a test case and will be included in the Summary report as a separate entry.

    • If the setting is disabled, the scenario outline will be treated as a single test case. The Summary report will include a single entry for the scenario outline.

  • Feature files cannot be marked as test cases. Scenarios they contain are always treated as test cases and are added to the Summary report.

  • Tags and tag expressions cannot be marked as a test case. Tests that match the tag or tag expression are always treated as separate test cases and are always added to the Summary report.

  • Regardless of this column value, TestComplete will generate a detailed test log for the test item anyway.

Execution entity The project item to be run. It can be:
  • a keyword test,
  • a script routine,
  • a BDD scenario or several scenarios,
  • a low-level procedure,
  • a network suite, or its job or task
  • a unit test or Selenium test,
  • a ReadyAPI functional or security test,
  • a tag,
  • a tag expression.

To choose a test, click the ellipsis button and use the resulting Select Test dialog.

Count The number of times the test will be repeated. Default is 1.
Timeout The maximum run time (in minutes) for the test item. If the run time exceeds the timeout, TestComplete posts an error to the test log and generates the OnTimeout event. You can create a handler for this event to stop the current test item and proceed to the next one. See Stopping Tests on Timeout.

Default is 0, which means no timeout.

Environments

The number of environments where cross-platform web tests will be executed. For non-cross-platform tests, values in this column will be set to 0.

To know how to add cross-platform environments and change them, see the Execution Plan Editor - Parallel Device Cloud Environments Panel.

For a description of the Parameters, On error, Link to external test case, On exception, and Description properties, see Execution Plan Editor - Properties Panel.

If a column is hidden, to make it visible, right-click anywhere in the editor, click Field Chooser, and then drag the needed column from the resulting list to the editor.

You can customize the column layout. For example, you can reorder or hide some columns. For more information, see Arranging Columns, Lines and Panels.

Common tasks

Add a new test item

Add a new group of test items that will be executed in sequence

Add a new group of test items that will be executed in parallel (for cross-platform web and mobile tests)

Modify test item properties

Rename a group

Copy an existing test item or group

Include or exclude test items from a test run

Mark a test item as a test case

Run a test item or group

Change the run order of test items

Navigate to the test source

Expand or collapse test items

Delete a test item or group

Save or cancel changes

See Also

Tests, Test Items, and Test Cases
Running Tests
Stopping Tests on Timeout

Highlight search results