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 test cases step by step in the built-in Test Player. Find your next test in seconds with search, My work, filters and Next to do, log a result per step, and report bugs to Jira pre-filled with the failed step - all without switching context.

Live preview - the real BesTest UI, running here

B
BesTest/Test Cycles/Test Player
Test Player•PHX-CY-22Sprint 24 regression
07:00
15 Tests•80%•3
9
2
1
1
0
2
Password complexity enforced
• 10min•
AR
Reset link expires after 24h
• 10min
ML
Invalid email inline error
• 5min
ML
Rate limit after 5 attempts
• 15min•1
DK
Lockout applies on all devices
• 10min•1
DK
Invoice matches the order
• 10min
ML
VAT is shown per line
• 5min
ML
Refund reverses invoice
• 15min•
?
Cart total follows quantity
• 5min
AR
Promo code at payment
• 10min
AR
Declined card can retry
• 10min180%•1
ML
Order email is sent
• 5min
DK
Saved card can be removed
• 5min
DK
Session times out when idle
• 15min
DK
Remember-me persists 30 days
• 10min210%
DK
Rate limit after 5 attempts
PHX-TC-320 • 2 executions in this cycle
PHX-EXEC-1298In ProgressRun 2 of 2
Objective:

Brute-force protection locks the account after repeated failures, and a locked account recovers cleanly.

Preconditions:

A registered account with a known password; rate limiting enabled on staging.

Assignee:DKDana K.
Test Steps
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
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
Enter the actual result observed during test execution...
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
Enter the actual result observed during test execution...
Execution Notes
Overall Execution Notes
Add overall notes about this test execution...

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

How It Works

The Test Player is where testers spend their day, so it is built to keep them moving. Pick a test case on the left (or press Next to do), start the run, and the Player assigns it to you and starts the timer. Each step shows its action, test data and expected result; mark it Passed, Failed, Blocked or Skipped, type the actual result, and the run's status follows from the step results. Click a result again to clear it. BDD test cases show their Feature and Background above the steps.

Large cycles no longer mean scrolling. Search across keys, names and execution notes, switch on My work to see only your test cases, or open the filter panel - status, has bugs, has a note, over time, tends to fail, retested, unassigned - with a count next to each. Next to do, also on the N key, takes you to the next open test, and the one you just finished stays open, marked as just finished. Reruns are one click away in the test case selector. The Player opens from everywhere you see a cycle or an execution - notifications, collections, reports - and Back returns you to where you were.

When a step fails, create a Jira bug right from the step. BesTest pre-fills the Jira create form: Bug type, a summary with the test case key and step, and a description with the cycle, test case, action, test data and expected vs actual result. The new issue is linked to the execution automatically. BesTest does not store attachments itself, so testers attach screenshots and logs to that Jira issue, where developers already look.

Two things keep results honest. If someone edits a test case's steps after the run was created, the Player shows a banner and lets you take the latest steps. And a cycle becomes Done when every test case has a result, but it still accepts notes, linked defects and time spent; adding test cases or starting a new run reopens it, and it closes again when everything has a result. Test leads follow along live in the cycle stats bar (progress and pass rate), the dashboard and Jira dashboard gadgets, without sending a single status-request message.

Key Benefits

Mark each step Passed, Failed, Blocked or Skipped and add the actual result - the run's status follows from the step results, and a built-in timer records how long it took.
Find your next test in big cycles: search keys, names and execution notes, switch on My work, or filter by status, has bugs, has a note, over time, tends to fail, retested or unassigned - each with a count.
Next to do jumps to the next open test, also with the N key, and the run you just finished stays open, marked as just finished.
Create a Jira bug from a failed step, pre-filled with the test case, cycle, step, test data and expected vs actual result, and linked back automatically. Attach screenshots to that Jira issue.
If a test case's steps change after the run was created, the Player tells you and lets you take the latest steps.
Done cycles stay useful: add notes, linked defects or time later, and adding new test work reopens the cycle automatically.

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