Creating a Project

Think of a project as a container for a single application or product that you want to test. Each project is completely independent, making it easy to organise different applications, teams, or customers without sharing data between them.

When should you create a new project?

In most cases, create one project per application or product.

For example:

• One project for your customer-facing website.
• One project for your admin portal.
• One project for your mobile web application.
• One project for each client if you're an agency or consultancy.

Keeping related tests together makes it easier to manage environments, test data, team members, and execution history.

Create a project

Creating a new project only takes a few seconds.

1. 1
   Open the Project Switcher.
2. 2
   Enter a project name.
3. 3
   Click on + icon.
4. 4
   You're ready to record your first test.

You can rename your project later from Settings → Manage Project.

What belongs to a project?

Each project contains its own resources, including:

• Team members and their roles.

  • Learn more about Roles & Members and Inviting Team Members.
• Test Suites, Test Cases, and Flows used to build and organise your automated tests.

  • See Test Suites, Test Cases, and Flows.
• Environments that define where and how your tests execute.

  • See Environments.
• Variables and Secrets used to store reusable configuration and sensitive information.

  • See Variables and Secrets.
• Run History and Reports for every test execution.

  • See Run History and Reports.

Project isolation

Projects are completely isolated from one another.

Resources created in one project are not shared with any other project, including:

• Test Suites
• Test Cases
• Flows
• Environments
• Variables
• Secrets
• Run History
• Reports
• Team members

This isolation helps keep applications, customers, and teams organised.

Deleting a project

Plan limits

Every project is subject to the limits of your current plan, such as the number of test suites, flows, environments, team members, and test executions that can be created.

For more information, see Plans & Usage.

Next steps