Run Test Execution
On a Test Execution, the Test Case Executions tab lists one Test Case Execution for each Test Case. From here, you assign them to testers, change their status, filter them, and open them to run the steps.
What a Test Case Execution is
A Test Case Execution (TCE) is a copy of a Test Case inside a Test Execution. It isn’t a Jira work item.
When you change a Test Case later, for example its steps or preconditions, the change doesn’t reach Test Case Executions that already exist. Otherwise, the change would alter tests that were already run. The TC Ver. column shows which version of the steps a Test Case Execution uses. See Steps Versioning.
The Test Case Executions table
The Test Management panel of a Test Execution has two tabs: Test Case Executions and Defects. The Test Case Executions tab shows:
- The ATM TE Progress bar.
- The Add Test Case and Add Test Plan buttons, and Test Cases in total. See Add Test Cases to an existing Test Execution.
- Filters above the table.
- The table with the TC Key, TCE Key, Summary, TC Ver., Iter., Defects #, TCE Status, Assignee, Executed By, and Actions columns.

In the Actions column, the … menu has New iteration and Remove. See Retests.
The Defects tab collects the defects from all Test Case Executions and the defects linked to the Test Execution itself. See Defects.
Open the execution window
In the row of a Test Case Execution, click â–¶. The execution window opens, where you run the test steps and set their statuses. See Test Steps Execution.
Assign, update, or remove several Test Case Executions
- In the table, select the Test Case Executions with the checkboxes.
- In the bar at the bottom, choose an action:
- Assign to assigns them to a tester.
- Change status changes their status.
- Remove removes them from the Test Execution.

Filter Test Case Executions
Filters help in a large Test Execution. For example, you can show only the failed Test Case Executions.
The filters above the table are TCE Status, Assignee, and Repository. More filters adds ATM Test Plans, Component, and Requirement. ATM doesn’t remember the filters you add with More filters. After you refresh the page or open another Test Execution, the table shows the three default filters again.
