> ## 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 test case status, evidence, and AI analysis for a single run. 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. ## 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 ### 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. ## 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. See more details at [Trace Viewer](/guides/playwright-trace-viewer).