About Test Executions

A test execution is an object used to plan a virtual or physical test and to capture whether the tests passed or failed.

See Also
Searching for Test Executions
In Other Guides
Content Categories

Test executions are tasks in a project linked to a parent test specification. You can assign and manage test executions within the project. If the test specification is not linked to a project, the test execution becomes a collaborative task. Each test execution has a pass/fail status that identifies the outcome of the tests performed.

Anyone can create the test execution collaborative task. However, you must have the project leader access role to create the test execution project task. An engineer with these credentials, such as the project leader or validation manager, then validates and verifies that the test results match the requirements.

Test Executions and Access Levels

Test executions (and all test objects) belong to specific content categories. The category of content, along with your access level, determines what actions you can take on the various types of content.

To create a test execution, you must have one of the following access roles:

  • Leader: Creates a task linked to a project.
  • Author: Creates a collaborative task (not linked to a project).

To review final test execution status, you must have the Leader access role.