App Repository & Test Files Sync
Connect the optional Git panels: a read-only App Repository that grounds the AI and maps coverage, and two-way Test Files Sync for the project's tests.
Last updated
Was this helpful?
⌘Ctrlk
Connect the optional Git panels: a read-only App Repository that grounds the AI and maps coverage, and two-way Test Files Sync for the project's tests.
Two settings panels connect a project to Git, and they are independent of each other. Settings → App Repository links the repository containing your application's own code — read-only. Settings → Test Files Sync mirrors this project's own test files to a repository you own — two-way. Both are optional; project content — features, generated tests, configurations, run history — always lives in TestVibe's cloud.
Settings → App Repository connects the repository that contains the application's code, on GitHub, GitLab, or Azure DevOps — one active source at a time. TestVibe reads it to ground the AI while generating and debugging tests, and to map coverage of your app's areas. TestVibe never writes to this repository, and repository permissions are requested only when you connect it — never at sign-in.
Settings → Test Files Sync mirrors this project's own test files — features, specs, and Playwright configs — to a GitHub, GitLab, or Azure DevOps repository TestVibe can write to. Edits flow both ways: changes made in the app push to the repository, and edits committed to the repository flow back into the project. TestVibe's cloud stays canonical. Write scopes are requested only when you enable sync.
These are two different corpora: the App Repository is your app's code (TestVibe reads it), while Test Files Sync carries TestVibe's own test files for this project (TestVibe writes and reads them).
Open a project.
Open Settings.
Select App Repository or Test Files Sync under the Project group.
Older versions kept these on a single Source Code page. They now live in dedicated panels:
Source repository / Git export (one Source Code panel)
Split into Settings → App Repository (read-only code context) and Settings → Test Files Sync (two-way mirror) — both described above.
Test site URLs
Settings → Environments — see Configure environments and App Repository.
AI agent, model, reasoning effort
Settings → AI Model — see Choose an agent and model.
Logins, tokens, test data
Settings → Variables & Secrets — see Add API keys and secrets.
Browser, viewport, run presets
Settings → Playwright — see Choose browser, viewport, and configuration.
Last updated
Was this helpful?
Was this helpful?