> For the complete documentation index, see [llms.txt](https://docs.testvibe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testvibe.com/readme/what-is-testvibe.md).

# What Is TestVibe?

TestVibe helps teams generate and run UI tests, load-test the same journeys, and watch live server telemetry — without making every tester start from a blank code editor or every engineer wire up k6 scripts and dashboards by hand.

You describe what your product should do. TestVibe helps organize that intent into a test suite, uses AI to generate Playwright code, runs the tests in isolated cloud test sessions against your site, and brings the results back into one place with screenshots, videos, traces, console output, and network details. The same flows can be replayed under load, and TestVibe streams telemetry from your running servers so you can see how they behave.

## The Short Version

TestVibe is for teams that want reliable UI test coverage, load testing, and server telemetry in one place — with a workflow that stays readable and repeatable inside your project in TestVibe's cloud.

Instead of separating test planning, test generation, test execution, and failure review across several tools, TestVibe gives you one workspace for the full loop:

1. Create a project with the URL of the site you want to test.
2. Create or organize tests in the Test Suite.
3. Write clear instructions for the behavior you want to validate.
4. Generate Playwright code with AI.
5. Run the test against your site in a cloud test session.
6. Review the result and evidence.
7. Edit, regenerate, or re-run as the product changes.

## How TestVibe Fits Into Your Workflow

TestVibe sits between your team and your application.

* Your team uses TestVibe to describe tests, start generation, run tests, and review results.
* Your project stores the feature files, generated Playwright tests, configurations, run history, and evidence — all in TestVibe's cloud.
* Isolated cloud test sessions run the tests against your site, with no CI pipelines or runners to set up.
* TestVibe shows live progress and makes the result easier to understand when something passes, fails, or needs attention.

GitHub is optional. You can sign in with it, point TestVibe at a read-only App Repository so the AI understands your app's code, or mirror the project's test files to a repository you own with two-way Test Files Sync — but none of that is required to test.

## What You Can Do With TestVibe

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Set up a testing workspace</strong></td><td>Create a project with the site URL(s) to test, then add the variables and secrets your tests need.</td><td><a href="/pages/AMnU2pTMCri7pum7FEH4">/pages/AMnU2pTMCri7pum7FEH4</a></td></tr><tr><td><strong>Create readable test intent</strong></td><td>Organize tests into groups, write clear instructions, use prerequisites, and record browser steps when that is faster.</td><td><a href="/pages/UxI3D69jP7OLADRoqvSd">/pages/UxI3D69jP7OLADRoqvSd</a></td></tr><tr><td><strong>Generate Playwright code</strong></td><td>Use AI to turn feature intent and test instructions into Playwright test files saved to your project.</td><td><a href="/pages/W3i7XJVOFjRvYAOMTe50">/pages/W3i7XJVOFjRvYAOMTe50</a></td></tr><tr><td><strong>Run and review tests</strong></td><td>Run one test, a group, or the full suite, then inspect failures with visual and technical evidence.</td><td><a href="/pages/jRDweXS74GF5RysL7hCO">/pages/jRDweXS74GF5RysL7hCO</a></td></tr><tr><td><strong>Load-test the same journeys</strong></td><td>Replay your feature flows under concurrent load, or run protocol-level k6 tests with threshold gates, and chart latency, throughput, and errors live.</td><td><a href="/pages/uBaJ99pd1DNU61PBtUWL">/pages/uBaJ99pd1DNU61PBtUWL</a></td></tr><tr><td><strong>Watch server telemetry</strong></td><td>Stream live telemetry from your running servers during runs and load tests to see how they behave under real traffic.</td><td><a href="/pages/iuokrOoXjDqouLfBml9Q">/pages/iuokrOoXjDqouLfBml9Q</a></td></tr></tbody></table>

## Who Uses It?

TestVibe is useful when different people contribute to testing in different ways:

* QA teams can plan tests, write instructions, run suites, and review failures.
* Product teams can express expected behavior in plain language before it becomes code.
* Developers can inspect the generated Playwright code in the app and optionally mirror it to their own repository (GitHub, GitLab, or Azure DevOps) with two-way sync.
* Team leads can track whether important flows are covered and whether recent runs are healthy.

## What Makes It Different?

TestVibe is built around the full testing loop, not just one step of it.

* It keeps test intent visible instead of hiding everything inside code.
* It uses AI generation to accelerate Playwright test creation.
* It runs tests in hardware-isolated cloud sandboxes built for AI-generated code.
* It load-tests the same journeys you already wrote, so functional and performance coverage share one source of truth.
* It streams live server telemetry alongside runs, connecting test outcomes to how your servers actually behaved.
* It keeps tests, runs, load tests, telemetry, and evidence together in one workspace.
* It brings failure evidence back to the people who need to understand what happened.

That combination makes TestVibe useful for both early test creation and ongoing test maintenance.

## Where To Go Next

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>If you are brand new</strong></td><td><ul><li><a href="/pages/0wx50YYwlfYEKP60cevN">Learn the key concepts</a></li><li><a href="/pages/kKNseH0YsIIMPDSgvnNe">Follow the quickstart</a></li><li><a href="/pages/Qj8uC4FMtg6Ddmqlc7k4">Sign in</a></li></ul></td></tr><tr><td><strong>If you are setting up a project</strong></td><td><ul><li><a href="/pages/Dmfrmb2QZrZR31qptfws">Create a new project</a></li><li><a href="/pages/OmsBY1OXulgZoZnkBH4o">Configure site URLs and project settings</a></li><li><a href="/pages/MI4twczuWahrBFSko238">Add variables and secrets</a></li></ul></td></tr><tr><td><strong>If you want to create a test</strong></td><td><ul><li><a href="/pages/XexYlPIo3LDGvD8cW94P">Create groups and tests</a></li><li><a href="/pages/33UtbH87hxyFCMYvvFyo">Write good test instructions</a></li><li><a href="/pages/EIYfDcimXldXAsAbHFsJ">Generate Playwright code</a></li></ul></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.testvibe.com/readme/what-is-testvibe.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.