Test Execution with Test Player

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.