Project is the highest level in the Allure TestOps hierarchy. A Project could contain the test for
a single service
a single feature
the data contained on a project level is the result of the agreement inside your team.
This page contains references to a project's settings available for a project Owner.
Creation of a project
In main Allure TestOps UI click + New Project button in upper right corner.
Name your project.
Add comments or description.
Decide whether it should be public or not (see Project visibility below for clarifications).
Hit Submit to start working on your new project.
Projects are private by default if not explicitly specified as Public.
Public projects are visible and accessible by every person that has an account in Allure TestOps.
Private projects are not visible for registered users if they aren't explicitly added to these as project team members.
Access to a project
As soon as a project created you need to provide the access to it to the team members.
You can read about the giving the access to projects here.
Abbreviation is 2 chars short project label.
Roles (Members) settings
Roles (Members) settings are related to the Ownership of the test cases created in the scope of the current project. These settings have nothing to do with the access rights and licencing of the instance. Here you will find the more detailed information on Roles (Members) settings of a project.
Test layer is another test's attribute allowing to mark a group test cases, e.g. API tests, UI tests, Unit tests.