Overview
The Stably Reporter is the hub for every test run—no matter whether you start in the Web Editor, the CLI, or with the Stably SDK. Use it to view test results, inspect logs, replay traces, and review any AI auto-heal fixes applied to keep your suite stable.See live runs, historical trends, and auto-heal changes in one place. Each run links back to the trigger (recorded in the web editor, launched via CLI, or executed with the SDK).
Send Runs to the Reporter
- Web Editor
- CLI
- SDK / Playwright
- Run or re-run a test from the Web Editor.
- The run automatically streams into the Reporter with screenshots, video, and AI heal attempts.
- Open Run details to inspect steps, logs, and any selector repairs the AI applied.
What You See
- Run summary: status, duration, environment, branch/commit, and who triggered the run.
- Artifacts: videos, screenshots, console/network logs, and Playwright traces for each test.
- AI auto-heal: every suggested or applied fix is recorded with before/after details so you can accept, revert, or copy the patch.
- Step-by-step replay: timeline of actions and assertions to pinpoint flaky or slow steps.
- Trends and flakiness: historical pass rates, retries, and slowest tests to guide stabilization work.
Review AI Auto-Heal Fixes
1
Open the run
Click the run link from the CLI output or from the Web Editor’s recent runs list.
2
Inspect failed tests
Expand any failure to see the DOM snapshot, logs, and the AI-proposed selector or assertion change.
3
Apply or copy the fix
Accept the auto-heal directly in the Reporter, or copy the suggested diff into your codebase if you prefer manual review.
Analytics for Teams
- Coverage over time: track how many tests run per day and how often they pass.
- Stability signals: identify flaky specs by retries and failure streaks.
- Execution health: monitor slow tests, error hotspots, and environments that need attention.