Test Player - Execution

Test Executions are individual records of a test case being run within a specific cycle.

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. This granular tracking enables precise failure analysis and detailed execution reporting.

Test Step Executions
Test Step Executions

Execution flow

  • Select a testcase on the left
  • 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
Execution flow
Execution flow

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

Execution flow
Execution flow

Features

  • Compact mode - maximum focus
  • Built-in Timer - precise execution times
  • Rerun any testcase
  • Automatic execution status based on step results
  • Report & Connect bugs
Getting started

Live in about a minute.

  1. ~30 seconds
    1.Install from the Marketplace

    One click on "Get it now" - no sales call, no signup form, no separate login.

  2. ~1 minute
    2.Enable it on a project

    Flip it on in project settings. BesTest shows up in the project menu, where your team already works.

  3. right away
    3.Run your first test

    Create a requirement, link a test case, hit run. No training course required.

Host your data in the EU, US, or IndiaNo Jira issue bloat - your library stays out of Jira’s wayBuilt on Atlassian Forge