Test Player - Execution

Test Executions

Test Executions are individual records of a test case being run within a specific cycle. Each execution tracks the result (Passed, Failed, Blocked, Skipped), assignee, environment, timing, and comments. Failed executions can be linked directly to Jira issues for defect reporting.

Test Step Executions

Test Step Executions capture the result of each individual step during a test case execution. They record whether each step passed or failed, the actual result observed, and any comments. Click a result again to clear it.

Execution flow

• Select a testcase on the left, or press Next to do
• Start execution on the right
  • Test case will be assigned to you
  • Timer will start
• Mark steps according to actual result
• Finish execution, continue with another test

In big cycles, use the search, My work (only your test cases) and the filter panel to find what to run next.

Reruns are shown in the test case selector. All reported bugs accessible by pressing the Bug icons.

When the test case changed

If a test case's steps were changed after the run was created, the Player shows a banner and lets you take the latest steps (or start a new run with them).

Features

• Full screen - maximum focus
• Search, filters and Next to do (keyboard shortcuts in the Next to do menu)
• Built-in Timer - precise execution times
• Rerun any testcase
• Automatic execution status based on step results
• Report & Connect bugs