Quickstart

Follow the fastest path from signing in to TestVibe to reviewing the result of your first generated Playwright test.

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)

• 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)

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 in

Sign in with email, GitHub, or Google to reach your workspace.

2. Create a project

Name the project and add the site URL(s) you want to test.

3. Create a test

Add your first Gherkin feature or test instructions in the Test Suite.

4. Generate code

Use AI generation to turn the test intent into Playwright code.

5. Run and review

Run the generated test in a cloud test session and inspect the result evidence.

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 problems

Check email verification and your sign-in method.

Generation cannot start

Check the variables and secrets your test references.

Run fails

Open the result evidence before changing the test.

Next

Start with Sign in.