# What is TestVibe? TestVibe helps teams create, generate, run, and review browser tests without making every tester start from a blank code editor. 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 through your connected GitHub repository, and brings the results back into one place with screenshots, videos, traces, console output, and network details. ## The Short Version TestVibe is for teams that want reliable UI test coverage, but also want the test workflow to be readable, repeatable, and connected to the repository where the tests actually live. 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. Choose a GitHub repository. 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. 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, your application, and your GitHub repository. * Your team uses TestVibe to describe tests, start generation, run tests, and review results. * Your repository stores the generated Playwright test files and the workflow configuration needed to run them. * GitHub runs the automation and keeps the test workflow connected to the same source control system your team already uses. * TestVibe shows live progress and makes the result easier to understand when something passes, fails, or needs attention. You do not need to understand the GitHub workflow details to use TestVibe day to day. The important thing is that TestVibe keeps the test assets in your repository while giving non-specialist users a friendlier way to create and inspect them. ## What You Can Do With TestVibe
Set up a testing workspaceConnect a GitHub repository, configure the site URL, and add the keys TestVibe needs for generation and runs./pages/AMnU2pTMCri7pum7FEH4
Create readable test intentOrganize tests into groups, write clear instructions, use prerequisites, and record browser steps when that is faster./pages/UxI3D69jP7OLADRoqvSd
Generate Playwright codeUse AI to turn feature intent and test instructions into Playwright test files stored in your repository./pages/W3i7XJVOFjRvYAOMTe50
Run and review testsRun one test, a group, or the full suite, then inspect failures with visual and technical evidence./pages/jRDweXS74GF5RysL7hCO
## 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 keep generated tests in GitHub and inspect the Playwright output when needed. * 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 stores generated test assets in your GitHub repository. * It lets you run tests from the same connected 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
If you are brand new
If you are setting up a repository
If you want to create a test
--- # Agent Instructions: 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: ``` GET https://docs.testvibe.com/readme/what-is-testvibe.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.