Set Up Your Workspace

Create a project with a name and the site URLs to test, organize your workspace, and optionally connect GitHub.

Your workspace is the container you work in and the projects inside it. A project is created in the app with a name and the site URL(s) to test — all content (features, generated tests, configurations, run history, evidence) lives in TestVibe's cloud. No repository is required.

Most setup happens once per project. After that, your team can create tests, generate Playwright code, and run the suite without repeating it.

Setup Path

Create a new project

Start a project with a name and the site URL to test.

Join an existing project

Accept a workspace invite or request access from a project link.

Configure environments and App Repository

Manage test site URLs and the optional source repository.

Connect GitHub (optional)

A read-only App Repository for AI context and coverage, and two-way Test Files Sync for this project's tests.

Manage members

Invite teammates, create a team workspace, and set Owner, Admin, Member, or Viewer roles.

Open the dashboard

Review project health and decide what to inspect next.

What TestVibe Needs

Requirement	Why it matters
Sign-in	Email/password, GitHub, or Google — identity only, no repository permissions. Followed an invite link? Sign-in shows the invitation itself and skips separate email verification.
A workspace	Every user gets a personal workspace; team workspaces are joined by invite, invite link, or created fresh (which can create its first project in the same step).
A project name and site URL	Your very first project is one screen — no repository required or offered. Additional projects add the same fields, plus an optional advanced source repository field.
A reachable site	The cloud test session must reach the URL; private apps use a tunnel device.

Where GitHub Fits

GitHub is optional, and there are two separate connections. Settings → App Repository links the repository containing your application's own code — read-only; the assistant reads it for context and coverage maps against it. Settings → Test Files Sync mirrors this project's own test files — features, specs, and Playwright configs — to a repository you own, with edits flowing both ways. Each is connected independently, and permissions are requested only when you enable it. See Connect GitHub (optional).

Where To Go Next

If you are setting up for the first time, start with Create a new project. If the project already exists, review Configure environments and App Repository.