Projects

Projects are containers for your test plans. Each project represents a web application, and can have one or more environments (e.g. prod, staging, uat). Each environment owns its own URL, notification config, test cookies/headers, and proxy country, so you can run the same test plans against different deployments.

Creating a Project

1. Go to Dashboard → Projects
2. Click Create Project
3. Fill in:

A new project is auto-created with a single prod environment. You can add more envs (and rename prod if you want) from the project edit page.

Environments

Environments are the unit you target with a run. Every project starts with a single prod env that picks up the URL and notifications from the create form. Add more (staging, uat, preview-*) from the project edit page when you're ready to test multiple deployments.

Each env carries its own URL, webhook / Slack / Teams config, test cookies, HTTP headers, and proxy country, so the same test plans target prod, staging, and uat with no edits to the plan itself. Pick the env at trigger time:

# Run all plans in the project against staging
curl -X POST https://test-lab.ai/api/v1/run \
  -H "Authorization: Bearer tl_xxxxx" \
  -H "Content-Type: application/json" \
  -d '{"projectId": YOUR_PROJECT_ID, "env": "staging"}'

Omit env to use the project's default. Pass an env name and the runner resolves it on every project the request touches, failing the whole batch if any project is missing it (so a CI mistake can't quietly run prod tests against the wrong target).

Project Organization Tips

For large applications, organize projects by feature area, then add environments inside each:

• MyApp - Auth → envs: prod, staging
• MyApp - Checkout → envs: prod, staging, uat
• MyApp - Dashboard → envs: prod

API Access

Projects can be accessed via the API using projectId:

# Run all test plans for a project
curl -X POST https://test-lab.ai/api/v1/run \
  -H "Authorization: Bearer tl_xxxxx" \
  -H "Content-Type: application/json" \
  -d '{"projectId": YOUR_PROJECT_ID}'

See API Reference for more details.

Metrics

Each project tracks:

• Test Plan Count - Number of test plans in the project
• Run Count - Total test executions
• Build Count - Unique build IDs (for CI integration)

Next Steps