> 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/quickstart.md). # Quickstart This quickstart walks you through the shortest successful path in TestVibe: 1. Sign in. 2. Create a project. 3. Create your first Gherkin test. 4. Generate Playwright code. 5. Run the test. 6. Review the result. You can come back later for deeper setup, generation, run, and troubleshooting details. For now, the goal is simple: get one useful test from idea to result. ## Before You Begin You will need: * a TestVibe workspace — sign up with email and password, GitHub, or Google, and every user gets a personal workspace automatically (if you're joining a team, an invite link takes you straight into their workspace instead — see [Sign in](/quickstart/sign-in-with-github.md)) * a project name and the URL of the site you want to test, reachable from the internet (private apps can come later with a [tunnel device](/account-settings/tunnel-devices.md)) That is it — there is nothing to install and no CI pipeline to configure. Your first project is one screen: name, site URL, and optional target framework — no source repository needed to get started. TestVibe will prompt for anything else missing as you move through the flow. ## Quickstart Path
1. Sign inSign in with email, GitHub, or Google to reach your workspace./pages/Qj8uC4FMtg6Ddmqlc7k4
2. Create a projectName the project and add the site URL(s) you want to test./pages/YDyXoHmaJyx0IzhVThDR
3. Create a testAdd your first Gherkin feature or test instructions in the Test Suite./pages/nRkMMo4g3K9NDlQ9RrsT
4. Generate codeUse AI generation to turn the test intent into Playwright code./pages/syTrwMhuGNSrbokqD1VH
5. Run and reviewRun the generated test in a cloud test session and inspect the result evidence./pages/7QdI4vUB8sdb0yMQU9UX
## What You Will Have At The End After the quickstart, you should have: * a project in your workspace * one Gherkin feature or test description * generated Playwright code saved to your project * one completed test run * result evidence you can use to decide what to do next ## If Something Blocks You Most first-run issues come from setup rather than the test itself.
Sign-in problemsCheck email verification and your sign-in method.
Generation cannot startCheck the variables and secrets your test references.
Run failsOpen the result evidence before changing the test.
## Next Start with [Sign in](/quickstart/sign-in-with-github.md). --- # 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/quickstart.md?ask=&goal= ``` `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.