For the complete documentation index, see llms.txt. This page is also available as Markdown.

Review Results

Read TestVibe run outcomes, inspect failed tests, and use screenshots, videos, and Playwright traces to understand what happened.

Use this section after a run starts or finishes. TestVibe brings the run status, test rows, charts, and evidence into one run detail view so you can decide what passed, what failed, and what to do next.

Start With the Run Detail

Open Runs, then select a run from the list. The run detail view shows:

Area
What it tells you

Summary tiles

Overall status, duration, selected files, and pass/fail counts.

Charts

Patterns across status, groups, projects, duration, and slow tests.

Features tab

Individual scenario rows and failed scenarios.

Images and Videos tabs

Browser evidence captured during the run.

Artifacts tab

Every file the run uploaded (screenshots, video, traces, logs), each downloadable — grouped by the scenario that produced it so you don't have to match filenames by hand.

Download menu

Export the run as JSON, CSV, Excel, PDF, or PNG.

Ask AI

Seeds the Assistant with a data-rich summary of the run — a quick way to get a plain-English verdict or share one with a teammate.

Common Review Tasks

A Good Review Flow

  1. Confirm the overall run status.

  2. Find the failed rows in the Features tab.

  3. Open the failed row details.

  4. Check the screenshot or video for visible UI state.

  5. Open the Playwright trace when the screenshot is not enough.

  6. Decide whether the issue is the app, the test, the environment, or the cloud test session.

  7. Re-run only after you know what changed.

For active runs, see Understand live run status.

Last updated

Was this helpful?