Choose a Source Repository (Optional)

Give a project an optional source repository so the assistant can read the application code when it explores your app or generates tests.

A source repository is the repository that contains the code of the application you are testing. It is optional — TestVibe stores all project content in its own cloud and never requires a repository, and it is never asked for during project creation itself.

When a project has one and you ask the assistant to explore your app — an on-demand action, not something that runs automatically when the project is created — it reads the code alongside the live site, which produces better-grounded feature suggestions and generated tests.

What The Assistant Does With It

What it reads	How it helps
Pages and navigation	Suggested features cover the flows that actually exist.
Forms and validation	Generated steps anticipate required fields and error states.
Domain language	Feature files use the names your app and team already use.

Without a source repository, the assistant still explores the live site and drafts features when asked — it just starts with less context.

When To Provide One

Situation	Recommendation
Your team owns the app code on GitHub	Provide it — the extra context is free.
The app is hard to understand from the UI alone	Provide it — code fills the gaps exploration misses.
You are testing a third-party or closed-source site	Skip it — exploration of the live site is enough.

Where To Set It

1. When adding a project from the workspace switcher, open Advanced settings and fill in the optional source repository field (not offered on the very first project's single-screen create form), or

2. Open Settings → App Repository in an existing project and set the source repository there — the more common path, since it works for the first project too.

Related Help

• Create a new project

• Connect GitHub (optional)

• App Repository & Test Files Sync settings