Review Your First Result
Open a finished run, read the summary — status, scenarios, duration, credits — then work through the evidence it captured: screenshots, a replay of the session, every network request, the browser console, and the downloadable artifacts.
After the run finishes, open the result details. This is where TestVibe helps you understand what happened.
The goal is not only to see pass or fail. The goal is to know what to do next.
Start With The Summary
Look for:
- overall status
- number of tests or scenarios that passed or failed
- run duration
- selected browser and viewport
- site URL
- any visible error or failure message
If the run passed, you can keep building coverage. If it failed, inspect the evidence before editing the test.
Review Evidence
Evidence is uploaded from the cloud test session to your project and viewed in the Runs section. Depending on the run and configuration, TestVibe may show:
| Evidence | How it helps |
|---|---|
| Screenshots | Show what the page looked like at important moments. |
| Videos | Replay the browser session. |
| Trace | Inspect Playwright actions, snapshots, and timing. |
| Console output | Find browser errors or warnings. |
| Network details | Check failed requests or unexpected responses. |
| Failure details | See which step or expectation did not pass. |
For deeper review guidance, see Review Results.
Decide What To Do Next
Use the result to choose the next action:
| If you see... | Consider... |
|---|---|
| The test passed | Add another test or run a group. |
| The expected UI did not appear | Check whether the application has a real issue. |
| The test clicked or checked the wrong thing | Improve the Gherkin instructions and regenerate. |
| Test data was missing | Update setup, prerequisites, or the target environment. |
| The site URL was wrong | Update the run or project settings and run again. |
| The generated code is close but not quite right | Edit the instructions, regenerate, or review the generated code. |
Build From Your First Run
Once one test works, the next step is to expand carefully:
- Add another scenario in the same feature.
- Generate and run it.
- Add a related group or feature.
- Run a small group.
- Move toward scheduled or full-suite runs when the basics are stable.
Next
You have completed the quickstart. Good next pages are: