BesTest Logo
BesTestTest Management for Jira
Feature

Test Execution with Test Player

Run through test cases step by step with the built-in test player

Run through test cases step by step with the built-in test player. Log results, link evidence through Jira issues, and report bugs - all without switching context. The test player guides testers through each step, making execution consistent and efficient.

Live preview - the real BesTest UI, running here

B
BesTest/Test Player
Sprint 24 regressionIn Progress
PHX-CY-22 21:40:12
81114
Rate limit after 5 failed attempts
PHX-TC-320 · 2 executions in cycle
New Run
Objective
Verify brute-force protection locks the account after repeated failures.
Assignee
D Dana K. Assign to me
1
Action
Submit a wrong password 5 times in a row
Test Data
user: demo@acme.io
Expected Result
Each attempt returns "invalid credentials"
Actual Result
OK - generic error shown each time
2
Action
Submit a 6th attempt
Test Data
same user
Expected Result
Account is locked; a lockout message is shown
Actual Result
Lock triggered on the 5th attempt, not the 6th
PHX-820 linked to this step
3
Action
Sign in with the correct password after the lockout window
Test Data
correct password
Expected Result
Access is granted; the failure counter resets
Actual Result
Click to add the actual result...

Not a screenshot - the same React components the app ships, with demo data.

How It Works

The test player in BesTest transforms test execution from a tedious manual process into a guided, efficient workflow. When a tester starts executing a test case, the test player presents each step one at a time with the expected result clearly visible. The tester marks each step as passed, failed, or blocked, building a complete execution record as they go.

When a step fails, the tester can create a linked Jira issue directly from the execution screen. The new issue is automatically populated with context from the test case - the step that failed, what was expected, and the test case reference. The tester can then attach screenshots and logs to the linked Jira issue, providing developers with everything they need to investigate. This tight integration means bug reports are detailed and traceable from day one, without requiring testers to copy-paste between tools.

Test execution progress updates in real time. Test leads and managers can see how far through a cycle the team is, which tests are passing, and where blockers have emerged - all without sending status-request messages to testers. The execution dashboard shows pass rates, failure trends, and cycle completion percentages, giving stakeholders the visibility they need to make informed release decisions.

Key Benefits

Step-by-step test player guides testers through each test case, reducing mistakes and ensuring consistent execution across the team.
Log pass, fail, or blocked status for each step - with the ability to create linked Jira issues for failures directly from the execution screen.
Real-time execution progress tracking lets test leads monitor cycle completion without interrupting testers.
Link evidence through Jira issues: create a bug from a failed step and attach screenshots, logs, or other evidence to the linked issue.
Full execution history is preserved for audit trails and trend analysis across releases.

Try Test Execution with Test Player in BesTest

Install BesTest from the Atlassian Marketplace and start using test execution with test player inside Jira in minutes. Free for teams up to 10 users.

Try BesTest Free
Read the docs

Explore other features

All features
Requirements Management with Coverage
Test Case Management with Folder Hierarchy
Smart Collections

Related Resources