> ## Documentation Index > Fetch the complete documentation index at: https://docs.testdino.com/llms.txt > Use this file to discover all available pages before exploring further. # Playwright Test Cases > Review a single test case in a run: its status, retry attempts, annotations, and the evidence TestDino captured. 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](/test-management/overview), 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](/guides/debug-playwright-failures/debug-with-ai). ## KPI Tiles Test case KPI tiles showing status, total runtime, and retry attempts ### 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. **Feedback on classification** For failed or flaky tests, use **Test Failure Feedback** to set the correct category and add context. This updates the current run and improves future classification. Test failure feedback form to set correct AI category and add context To record your team's own label for the failure, use **Set defect type** in the **Status** card. See [Defect types](/guides/debug-playwright-failures/defect-types). ### 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: | Verdict | What it means | | :- | :- | | **Every attempt failed the same way** | The failure is consistent, so a retry will not clear it | | **Attempts failed for different reasons** | Inconsistent failures usually point to flakiness, not a fixed bug | | **Failed more than one way before passing** | Each failure is a separate cause, so fixing one may not stop the rest | | **Attempts could not be compared** | At least one attempt recorded no readable error, so any match would be a guess | 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](/guides/playwright-test-annotations) for setup instructions and all supported types. ## Evidence Evidence panel showing tabs for each attempt with error details, steps, screenshots, console, and video [Evidence](/guides/debug-playwright-failures/visual-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](/guides/debug-playwright-failures/visual-evidence#enable-screenshots). ### 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](/guides/debug-playwright-failures/visual-evidence#enable-video-recording). ### Trace Shows the Playwright trace for the attempt when available. Use it to inspect actions, network calls, console output, and DOM snapshots. Trace inspection is covered in the [trace viewer guide](/guides/playwright-trace-viewer).