Create a New Project
Create a TestVibe project in the app with a name and the site URL to test — no repository required.
A project is created directly in the app with a name and the site URL to test. All project content — feature files, generated tests, configurations, run history, and evidence — lives in TestVibe's cloud.
If this is the very first project on your account, TestVibe shows this as a single onboarding screen automatically right after sign-in — name, base URL, and optional target framework, nothing else. What follows below is the same minimal form, reached instead from the workspace switcher for adding another project to an account that already has one.
Before You Start
A project name
How the project appears in the workspace switcher and project list.
A base site URL
The application address your tests open. More URLs can be added later in Settings → Environments.
Optional target framework(s)
Helps TestVibe read your app's UI; TestVibe also auto-detects on the first visit.
Optional source repository
Only offered under "Advanced settings" when adding a project from the header — not part of the first-run screen. Lets the assistant read the application code for context. Can always be added later in Settings → App Repository instead.
Steps
Sign in to TestVibe.
Open the workspace switcher in the header and select New project.
Enter a clear project name.
Enter the base URL of the site you want to test.
Optionally pick target framework(s).
Optionally, open Advanced settings to add a source repository URL or clone features from an existing project.
Create the project.
Creating a project is instant and free — it does not spend credits and does not probe the site. You land in the new project on the Test Suite (Features) with the Describe a flow dialog open, ready to write your first test.
After Creation
Open the new project and confirm:
the site URL is correct — add more environments in Settings → Environments
teammates who need access are invited from Settings → Members
If you want TestVibe to explore the live site and suggest tests to cover it, trigger that from the assistant whenever you're ready — it no longer runs automatically on creation.
If the site is not reachable from the public internet, connect a tunnel device — see Tunnel devices.
Naming Tips
Use a name that makes the project's purpose obvious to teammates — the app or product area it covers, such as customer-portal or billing-checkout. Avoid temporary names unless you truly intend to replace the project.
Related Help
Last updated
Was this helpful?