Project Configuration

Which project wide configuration options you have and how to use them.

To configure either a load test or monitoring project, select Configuration in the project menu on the left. In the project configuration, there are several tabs for all kinds of settings that will be applied globally to the project. The contents and possible settings differ slightly depending on the project type (load test or monitoring), but most are fairly similar. For settings that are only available for a specific project type, please check out load test project configuration or monitoring project configuration.

General

In the General tab, you can edit the project name and upload a project logo.

To use this feature, your account must have the role of a project administrator within the project.

For monitoring projects, this tab will additionally contain information on data persistence and the execution environment where the monitoring scenarios are running in. These settings are for your information only and can be changed by XTC administrators only.

Repository

To view repository settings, your account must at least have the role of a tester within the project.

To edit repository settings, your account must at least have the role of a test manager within the project.

In Repository, you can define where the test suite repository is located, which branch should be used and how to resolve the test suite root within the repository. If the access to the remote repository is restricted, you can also provide authentication details.

The repository branch name for load test projects is always of type fix/static; however it is possible to override this branch name by a specific branch setting for each load test. This is not possible in monitoring projects, but in this case you have the possibility to configure the branch name to be determined dynamically in the project settings, by defining a URL of a resource from which the branch name can be extracted using a regular expression. This may be useful if you want to make the used test scenario code dependent on your currently deployed app version.

To add or change repository authentication info, click the editing button:

You can choose between entering either credentials (username and password, which can also be a token name and value if your repository is using limited access tokens) or an SSH Key (with username and passphrase). To confirm your changes, click “Accept”.

Last modified January 13, 2022