Projects

What is a project

A project is a container that holds all the testing work for a specific application or service. Everything in qtrl is organized within projects: your tests, tasks, test runs, environment configuration, and team assignments all live under a project.

Most teams create one project per application they are testing. For example, if your company has a customer-facing web app and an internal admin dashboard, you would typically create two separate projects for those.

Project settings

Every project has a few core settings that you configure when creating it and can update at any time from the project's Settings tab:

• Name: a descriptive name that helps your team identify the project at a glance.
• Description: a brief summary of what application the project covers and its scope.
• Default environment: the environment that is pre-selected when creating new tasks or test runs. You can always override this per task.

Environments

Each project supports four environments. These represent the different stages where your application runs and where tests can be executed:

• Development: for local or early-stage environments where features are being built. Useful for quick validation during development.
• Test: a dedicated testing environment, often used for integration testing or QA team workflows.
• Staging: a pre-production environment that mirrors production as closely as possible. Ideal for final validation before releases.
• Production: the live environment. Use this for smoke tests, monitoring, or verifying deployments after release.

When you create a task or start a test run, you select which environment it should run against. This ensures tests are executed in the right context with the appropriate configuration.

Environment variables and secrets

Projects support environment-specific configuration through variables and secrets. These are managed from the project's Settings tab under the environment configuration section.

Environment variables are key-value pairs that the AI agent can use during test execution. For example, you might set a BASE_URL variable for each environment so tests automatically target the correct URL. Variables are visible to project members and can be updated at any time.

Secrets work similarly but are encrypted and cannot be viewed after creation. Use secrets for sensitive values like test account credentials or API keys. If you need to change a secret, you delete the existing one and create a new one.

Team access

Projects inherit the team from your organization, but you can control which members have access to each project. From the project's Members tab, you can assign or remove organization members.

This is useful when your organization has multiple teams working on different applications. Each team only sees and works with the projects relevant to them. Organization owners and admins always have access to all projects.

For more on how organizations and roles work, see the Getting Started guide.