V
Vibeview
Pricing
Sign In

Tests Dashboard

The Tests dashboard (/tests) provides an org-wide view of all test suites, standalone tests, and test maintenance across every app in your organization. It is the central place to monitor test health and quickly identify failures.

Tabs

The dashboard has four tabs:

  • Suites — All test suites with their status, run history, and analytics.
  • Standalone — Individual test cases that run independently, outside of any suite. Useful for one-off tests, CI-triggered tests, or tests created by external agents.
  • Sub-Flows — Reusable standalone cases that other cases include as building blocks (for example, a shared login flow). See Sub-Flows.
  • Maintenance — Flaky and failing tests that need attention, with auto-heal suggestions.

Tab selection persists in the URL (e.g., /tests?tab=standalone), so you can bookmark or share direct links to any tab.

Suites Tab

When you open the Suites tab, you see a table of all test suites. Each row shows:

  • Suite name and the app it belongs to (clickable link to the app).
  • Number of test cases in the suite.
  • Latest run status — the result of the most recent run (passed, failed, error, or pending). A passed run with unresolved visual drift is shown in yellow (“passed with warnings”) — see Run status colors.
  • Last run date — when the suite was last executed.
  • Created date — when the suite was first created.
  • Delete action — trash icon to remove orphaned or unused suites.

Features

Status filtering

Use the status filter dropdown to narrow the list:

  • Failed — suites that need attention.
  • Passed — suites that are green.
  • Error — infrastructure or unexpected issues (session timeout, simulator crash).
  • Pending — suites created but never run.

Tags

Test suites can be tagged for organization and CI filtering.

Adding tags:

  • On suite create, type tag names in the Tags field. Press Enter or comma to add a tag chip; Backspace on an empty input removes the last chip. Clicking outside the input also commits whatever you’ve typed.
  • On the Suite Detail page, click Add tags (or Edit next to existing tags) to use the same picker inline. Each chip is saved automatically as soon as it’s added — there’s no separate Save step. Click Close when you’re done.
  • A suggestions dropdown appears as you type, listing existing tags in your organization with their usage counts. Click one to use it.
  • Tags are case-insensitive — Profiles and profiles resolve to the same tag. The original casing is preserved as the display name.
  • Allowed characters: lowercase letters, digits, hyphen, and underscore. Maximum 50 characters per tag.

Filtering by tag:

  • The tag pill bar above the suite list shows every tag in your organization with its usage count.
  • Click a pill to filter the list. Selecting multiple tags shows suites that match any of them (match=any).
  • The selection is stored in the URL (?tags=...), so you can share or bookmark a filtered view.
  • Click Clear to remove all tag filters.

From CI: see CLI: run-suites for running tag-filtered suites in pipelines (vibeview run-suites --tag profiles).

Delete suites

Click the trash icon on any suite row to delete it. A confirmation dialog appears before deletion. This is useful for cleaning up orphaned suites (e.g., suites whose app was deleted).

Import YAML

Click the Import YAML button at the top of the dashboard to import a test suite from a YAML file. The file should be in VibeView’s YAML test format (exported from another VibeView instance or hand-written). If the YAML includes an appId field matching an app in your organization, the suite is automatically linked to that app.

Drill-down to suite detail

Click any suite to navigate to its Suite Detail page (/tests/:suiteId).

Standalone Tab

The Standalone tab shows test cases that are not attached to any suite. Standalone tests can be run independently, triggered from CI pipelines, or created by external AI agents.

Viewing standalone tests

Each row in the standalone tests table shows:

  • Name — the test case name.
  • App — the app the test runs against (clickable link to the app detail page).
  • Steps — number of steps in the test case.
  • Recent Runs — the last 10 run results displayed as colored dots (green = passed, red = failed, yellow = other). This sparkline gives you a quick visual of recent test health.
  • Created — when the test was created.
  • Actions — run (play button) and delete (trash icon) per row.

Creating a standalone test

Click the Create Test button to expand the inline creation form. Fill in:

  • Name (required) — a descriptive name for the test, up to 200 characters.
  • App (required) — select the app to test from the dropdown.
  • Steps (required) — enter test steps, one per line. Each line becomes an AI-driven step instruction (e.g., “Open the app”, “Tap on Login”, “Enter credentials”).
  • Context (optional) — additional context for the AI agent, such as app-specific terminology or expected behavior.

Click Create Test to save. The new test appears in the table immediately.

Running a standalone test

Click the play button on any standalone test row. VibeView triggers a test run and navigates you to the dedicated run detail page (/tests/runs/:id) where you can watch progress in real time.

Deleting a standalone test

Click the trash icon on any row. A confirmation dialog appears before deletion. Deleting a standalone test also removes all its run history.

Suite Detail Page

The suite detail page (/tests/:suiteId) opens to a consolidated header with the suite’s content organized into four tabs:

  • Cases — the test cases in the suite.
  • Configuration — the suite’s run settings (see Configuration tab).
  • Analytics — the stats cards and trend charts (see Stats cards and Charts).
  • Runs — the run history (see Run history).

The header sits above the tabs and stays visible across them. It holds:

  • Suite name — click to rename inline.
  • Description — click the text (or the “Add description…” placeholder) to edit inline. 2000-character limit; Save persists, Cancel reverts.
  • Tags — chips below the description. Click Edit or Add tags to open the tag picker; each tag saves as soon as you add it. See Tags above for the full picker behavior.
  • A summary line showing the suite’s app, reset strategy, and last run status.
  • Action buttons: Run Suite, Export YAML, and Delete.

Run Suite

The Run Suite button opens the suite in the device sandbox, where you choose the execution mode and start the run. It is disabled until the suite has an app assigned (the tooltip explains why). The run controls — including aborting an in-progress run — live in the sandbox; see Device Sandbox.

Configuration tab

The Configuration tab holds the settings that apply to every run of the suite:

  • App under test — which app build is installed and run. Required before the suite can run.
  • Reset strategy — how device state is reset between cases: none, relaunch the app, clear app data (default), or full reinstall.
  • AI agent context — free-text notes injected into the agent’s prompt on every step (e.g. app-specific terminology).
  • Variables — key/value pairs you reference in steps as {{key}}.
  • Visual regression — the warn and fail drift thresholds, each independently enabled. See the visual regression guide.

Changes on this tab are saved together with the Save Configuration button — they do not auto-save.

Run status colors

A passed run that still has unresolved visual drift (drift past the warn threshold but below the fail threshold) is shown in yellow rather than green, as a “passed with warnings” signal. The run’s status is still passed — the color is the at-a-glance cue to review the flagged steps. Cancelled runs are shown in neutral gray. See visual regression for what drives the warning.

Export YAML

Click Export YAML on the suite detail page to download the suite and all its test cases as a YAML file. The export includes recorded gestures, step mappings, and device dimensions — everything needed for hybrid replay on another VibeView instance.

Stats cards

Six cards at the top summarize suite health:

  • Pass Rate — percentage of passing runs.
  • Total Runs — count of all suite and individual runs.
  • Avg Duration — mean run time across all runs.
  • Total Cost — accumulated cost across all runs.
  • Test Cases — number of cases in the suite.
  • Flakiness — percentage of runs with inconsistent results.

Charts

Four interactive charts:

  • Pass/Fail Trend — bar chart of pass vs fail over recent suite runs.
  • Duration Trend — line chart of run duration over time.
  • Cost Trend — line chart of cost per run over time.
  • Case Reliability — bar chart of per-case pass rates.

Run history

A chronological list of all runs. Each run shows status, duration, cost, and model used. Suite runs are expandable to show per-case results. Individual test case runs display inline with their case name and pass/fail result.

Clicking any run navigates to the dedicated Run Detail page (/tests/runs/:id) where you can see the full step timeline, AI reasoning log, and visual regression results. The URL is shareable — send it to a teammate or bookmark it for later review.

Visual regression status

Runs in the suite detail page’s run history display a small colored dot next to their status when visual regression is enabled on the suite:

  • Red dot (tooltip: Visual regression failed) — at least one step crossed the fail threshold and the run aborted. The run status itself is failed.
  • Yellow dot (tooltip: Visual drift detected) — at least one step crossed the warn threshold. The run completed; review the flagged steps.
  • No dot — the run passed visual regression or did not run it.

The same dot appears on the run tables in Test Case Detail and Standalone Test Detail pages. The top-level Tests dashboard shows suite-level statuses only; drill into a suite to see per-run visual dots.

Full detail on thresholds, per-step verdicts, and accepting new baselines lives in the visual regression guide.

Build reference

Each run records which build of the app was tested. The run detail page (/tests/runs/:id) shows the build version and, when present, the build number. The build label links back to the app’s Build History tab so you can see what was in that upload.

Full detail on builds, notes, and per-build runs lives in the apps guide.

Actions

  • Delete suite — remove the suite and all its data.
  • Navigate to cases — view and manage individual test cases.

Tips

  • Check the Tests dashboard after deployments to catch regressions early.
  • Use status filtering to build a daily routine: filter by failed, investigate, fix, re-run.
  • If a suite shows error status, the issue is likely infrastructure-related rather than a test logic problem. Check the run details for specifics.
  • Suites that have never been run show pending status. Run them at least once to establish a baseline.
  • Delete orphaned suites (those with no app) to keep the dashboard clean.