CoverIt is developed as several repositories placed next to each other in one parent folder. The full local setup runs the app stack, crawler worker, DocGen worker, and regression worker at the same time.
Install these tools before running the system locally:
| Tool | Purpose |
|---|---|
| Git | Clone and manage repositories. |
| Docker Desktop | Run the main app stack and databases. |
| Node.js and npm | Run the frontend, API, regression generator, and shared packages. |
| Python 3.12+ | Run the crawler and DocGen workers. |
| uv | Manage Python dependencies. |
| Git Bash or WSL on Windows | Run shell scripts such as docker.sh and run-regression.sh. |
Clone the repositories into one parent folder:
CoverIt/
.github/
coverit-api/
coverit-contracts/
coverit-crawler/
coverit-docgen/
coverit-frontend/
coverit-regression/
coverit-regression-framework/
The services expect this sibling layout during local development.
Each service has its own environment configuration. Use the example files in each repository when available, then fill in local values for database URLs, Redis, Neo4j, service tokens, OAuth providers, email settings, and repository access.
Use local environment files for real secrets. Keep documentation and examples limited to dummy values.
Open four terminals from the parent folder.
cd coverit-frontend
./docker.sh up --local --app-onlyThis starts the main application stack and supporting services such as the API, frontend, Postgres, Redis, and Neo4j.
cd coverit-crawler
uv sync
source .venv/Scripts/activate
python scripts/run_local_worker.pyThe crawler worker handles automatic crawl jobs, Playwright browser control, and manual recording sessions.
cd coverit-docgen
uv sync
source .venv/Scripts/activate
python scripts/run_local_worker.pyThe DocGen worker labels graph data and generates documentation and video artifacts.
cd coverit-regression
npm install
npm run workerThe regression worker generates regression code from reviewed flows.
After the services are running, open:
http://localhost:5173
Create an account, create a project, add a target application, add a version, and start with either an automatic crawl or manual recording.
- Start the app stack.
- Start the crawler, DocGen, and regression workers.
- Open the frontend.
- Create a project and application version.
- Configure the regression codebase.
- Run a crawl or manual recording.
- Review generated flows and assertions.
- Generate regression code.
- Run the generated regression suite when needed.