Projects

Project

Project is the core of the service. It is the only entity that stands on its own. All other objects are project dependents.

Testcases, testssuites, testruns - they all are sub-entities of the project belonging to a single one.

A new project could be created by a system administrator only. Administrator grants initial permissions on the project to a group (groups) of users who will be able to update it in the future.

There is no limitations of how many projects could be created. Project entities don't have any intersections between objects from another project.

On logging in a user will be asked to select a project he would like to work with.

Current project could be changed any time by clicking on the list of projects in the header menu or by selecting one on a projects page, available from the same header menu.

All URLs inside the service are build accordingly and contain the project id. E.g.: QUACK_DOMAIN/api/{PROJECT_ID}/testcases

Settings

Project settings could be altered by system administrator or any user, who has permissions to update the project (is in one of the groups selected for the project).

Go to "All projects" and click on a "gears" link to access project's configuration.

Allowed Groups

Groups of users who have read-write access to the project

Environments

List of default environments used to trigger Launches. This list will be visible in a selector when creating a launch. Multiple environments could be selected for a single Launch. In that case one launch per environment will be created

Launchers

Pre-configured external launch plugins. Configured Launchers will be available to select on Launch creation