Projects and collaboration

A project is the main collaboration and permission unit in Allure TestOps. It defines who can see the work, who can change it, and where launches, test cases, dashboards, and integrations belong.

Decide what belongs in the same project

• one project per product;
• one project per service or subsystem;
• one project per team or product area.

A good project boundary keeps launch history, test assets, and access rules useful to the same people.

Keep tests in the same project when they need shared analytics, dashboards, launch history, or access rules. Separate them into different projects when test assets, permissions, or reporting scopes must stay independent.

Set up the boundary that the project holds

Create and manage projects

Project access and visibility

Project notifications

What a consistent project should contain

Use the same project for assets and decisions that belong to the same working group:

• launches that should share history, dashboards, and analysis;
• test cases and shared steps that belong to the same testing scope;
• dashboards and defects that describe the same testing scope;
• integrations used by that scope.

If the project scope is defined and you are ready to dive into project work, continue with Execution and reporting or Test management.