How to Get a Usable Report Out of a Playwright Run

A test result is more useful when it tells you what ran, what passed or failed, how long it took, and where the failure occurred. A basic pass/fail status is not enough when you need to investigate or share results.

Leapwork Play brings the execution and reporting view into the same workflow. You can review run status, test-level results, execution details, and reporting metrics without building a separate reporting workflow around the test.

Try Leapwork Play →

How do you review a Playwright run in Leapwork Play?

To review a Playwright run in Leapwork Play, open the relevant RunList, go to the Run log, and select the run you want to investigate.

Review a Playwright run step by step

Use the run view to check the result, find failing tests, and inspect the exact step that needs attention.

Check the overall pass or failure status to understand whether the Playwright run succeeded.
Review the test cases included in the run to identify which tests passed, failed, or require follow-up.
Open the step-level execution details to see exactly where the run failed.
Watch the captured execution video to reproduce the behaviour visually.
Use the error details for failed steps to diagnose the root cause and decide the next action.

This workflow helps you move quickly from the overall Playwright run result to the failed test case and the exact step that needs investigation.

How to read a useful Playwright test report

Use the report to answer these questions quickly:

Check the overall result — see how many tests passed, failed, skipped, or stopped.
Review the execution time — confirm how long the run took and whether it looks unusual.
Scan test-level results — identify which test cases succeeded and which ones failed.
Investigate failures first — use the error message, trace, screenshot, or video to understand what happened.
Compare trends — check whether failures, flakiness, or run duration are increasing over time.

Focus question:

What happened during this run, and where should I investigate first?

How to understand Playwright test results in Play

The Reporting view in Play turns Playwright test execution data into an easy-to-scan dashboard for the selected run set. Use it to quickly check test health, identify failures, and decide whether you need to investigate a specific run.

What the Reporting dashboard shows

Number of runs in the selected run set
Total Playwright test cases executed
Passed, failed, and stopped tests
Average test duration
Overall pass rate
Status and severity distribution
Execution source
Run-duration trends
Selected test cases for deeper analysis

Example Playwright test report summary

A report can immediately show the key quality metrics for a run:

Runs:          1
Total tests:   1
Passed:        1
Failed:        0
Stopped:       0
Pass rate:     100%
Avg duration:  49.6 s

How to drill down from the dashboard

Start with the dashboard for a high-level Playwright report summary. Then open the Run log when you need to review the individual execution details behind a result.

How to investigate failed Playwright tests

Follow this workflow to move from the summary view to the exact failure details:

Open the Reporting dashboard to review the overall run status and pass rate.
Go to the Run log to find the specific execution that needs attention.
Open the affected test case.
Review the available steps, video, and error details to understand the root cause.

This workflow keeps the article searchable for common queries such as Playwright test results, test reporting dashboard, run log, failed tests, and debugging Playwright failures.

Tip: For a failed test, do not rely only on the final status. Open the test case in the Run log and inspect the steps, video, and errors to confirm what failed and why.

How Play extends the Playwright reporting workflow

Playwright	Leapwork Play
Generate and consume test results	Review results through the Play execution workflow
Review pass/fail outcomes	See run-level and test-level results
Investigate individual failures	Open the failed test and inspect steps, video, and errors
Build separate reporting views as needed	Use the Reporting dashboard for run metrics and trends

Play keeps Playwright underneath while bringing execution results and reporting into the same test workflow.

Best practices

Start with the Reporting dashboard, then drill into the Run log when a test needs investigation.
Check test-level results rather than relying only on the overall pass rate.
Use step details and execution video to understand failures.
Review duration trends when test execution becomes slower over time.
Share the report summary when stakeholders need the overall result and use the Run log for technical investigation.

Troubleshooting

Problem	What to check
Run shows failed tests but the cause is unclear	Open the affected test case in the Run log and inspect its steps and errors.
Overall run passed but a test needs investigation	Review the individual test execution rather than relying on the run summary.
Test duration is increasing	Check the duration trend in the Reporting view.
You need to understand what happened during a failed step	Review the available step details and execution video.

Frequently asked questions

What should a Playwright test report contain?

At minimum, it should show the overall result, test-level status, execution duration, and enough information to investigate failures.

How does Leapwork Play report Playwright test results?

Play provides run-level and test-level reporting through the Run log and Reporting views, including execution status, duration, step details, video, and errors.

Can I see what happened during a failed test in Play?

Yes. Open the run in the Run log and inspect the test's steps, video, and errors.

What is the difference between Run log and Reporting?

Run log is for investigating individual executions. Reporting provides a higher-level view of metrics, status distribution, duration, and selected test cases.

How do I get from a failed run to the root cause?

Start with the failed run, open the affected test case, and inspect the steps and execution evidence around the failure.