Projects

A project is the top-level container for testing a specific application or service.

Creating a Project

1. Navigate to your workspace
2. Click New Project
3. Fill in the project details:
   • Name - A descriptive name (e.g., "E-commerce Staging")
   • Description - Optional description
   • Base URL - The URL where tests will run

Project Settings

Base URL

The base URL is where tests start. Examples:

• https://staging.myapp.com
• https://preview-pr-123.myapp.com
• http://localhost:3000 (for local testing)

Authentication Settings

Configure default credentials for tests that require login:

Setting	Description
Email	Default email for login steps
Password	Default password for login steps
Storage State	Saved cookies/session from login suite

Storage State

Storage state contains cookies and local storage from a login suite run. When set:

• Tests start with an authenticated session
• No need to repeat login steps in every test

Project Integrations

GitHub

Connect your GitHub repository to:

• Receive PR comments with test results
• Trigger tests on deployments
• Show commit status checks

Slack

Send test result notifications to a Slack channel.

Email

Receive test reports via email after each run.

Vercel / Netlify

Automatically trigger tests when new preview deployments are ready.

API Keys

Generate API keys to trigger tests from CI/CD pipelines:

1. Go to Project Settings → API Keys
2. Click Generate New Key
3. Copy the key (shown only once)
4. Use in your CI/CD pipeline

See API Keys for usage details.

Archiving Projects

To archive a project you no longer need:

1. Go to Project Settings
2. Click Archive Project
3. Archived projects are hidden but can be restored

Best Practices

• One project per application - Don't mix different apps in one project
• Use descriptive names - "Checkout Flow - Staging" is better than "Test Project"
• Configure integrations early - Set up GitHub and Slack before creating tests
• Use environment-specific projects - Separate staging and production if needed