Playwright Test Cases

The Test Case view shows one test result within a test run. Review status, failure cause, runtime, retry attempts, and evidence (screenshots, videos, traces) for each attempt. This differs from Test Case Management, which organizes manual test cases.

​

Move between test cases

The header shows your position in the test run as Test 4 of 21. Use the arrows to step to the previous or next test case. They walk the whole test run, so you never skip a test case. Click the position label to open the search popover. Search by test case title, or switch between All, Failed, and Flaky to narrow the list. Those tabs filter the list you are picking from. The arrows still walk the full test run. On a failed or flaky test case, the header also carries Debug with AI, which hands that test case to your AI assistant. See Debug with AI.

​

KPI Tiles

​

Status

Outcome for this run: Passed, Failed, Skipped, or Flaky. For failed or flaky tests, the primary technical cause is shown.

​

Why Failing

AI category for the failure: Actual Bug, UI Change, Unstable Test, or Miscellaneous. Includes a confidence score. Use this to decide whether to fix the product code, update the test expectations, or stabilize the test.

​

Total Runtime

Total execution time for this test in the current run. Useful for spotting slowdowns after code or configuration changes.

​

Attempts

Number of retries executed by your retry settings. A pass after a retry often signals instability that needs cleanup.

​

Compare attempts

When a test case ran more than once, a card above the evidence compares what went wrong in each attempt and tells you whether the failure is consistent: Each distinct cause is listed below the verdict with the attempts it affected, such as Run and Retry #1. Expand one to read its stack, or open Full stack for the untruncated text. The card does not appear when a test case ran once, and it reports a verdict only when the evidence supports it. A test case that failed then passed on retry shows nothing here, because the attempt tabs and the Flaky status already say so.

​

Annotations

If your Playwright test includes testdino: annotations, they appear in the Annotations panel just below the KPI tiles. This panel displays all the metadata attached to the test: priority, feature area, ticket link, owner, Slack notification targets, context notes, and flaky reason. These annotations come from your test code and are read-only in the UI. To add or change them, update the annotation array in your test file. See the Annotations guide for setup instructions and all supported types.

​

Evidence

Evidence is grouped by attempt, for example, run, retry 1, retry 2.

​

Error Details

Exact error text and key line. Copy this into a ticket or use it to reproduce locally.

​

Test Steps

Shows the step list with per-step timing. Use it to locate where the failure occurred.

​

Screenshots

Screenshots captured during the attempt. Use them to confirm UI state at the time of failure. For a detailed guide, see Visual Evidence.

​

Console

Shows browser console output. Use it to correlate script errors or warnings with the failure.

​

Video

A recording of the attempt. Use it to confirm the sequence of actions and timing across retries. Know more about videos at Visual Evidence.

​

Trace

Shows the Playwright trace for the attempt when available. Use it to inspect actions, network calls, console output, and DOM snapshots. See more details at Trace Viewer.

​

Text attachments

Text files your test attaches, such as logs, JSON payloads, or Markdown notes, are listed with the rest of the evidence. Screenshots, video, and traces have their own sections above. Click one to read it in place instead of downloading it to check a single line. Each attachment also has a Download link. A file over 512 KB shows its first 512 KB with a note saying so; download it for the rest. If a download fails, the page reports Could not download the file. Refresh the page and try again.

​

Visual Comparison

Snapshot comparison for tests that use Playwright visual assertions, for example, toHaveScreenshot. See more details at Playwright Visual Testing. Use the viewer to compare screenshots in these modes:

​

Related