Project Configuration
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.
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
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. For load test projects, this section also allows you to define which build tool to use and to clear the dependency cache if necessary.
Branch
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.
Repository Authentication
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”.
Please note that when using an SSH key for authentication, you need to enter the matching SSH repository URL above, while user credentials or access tokens require an HTTPS repository URL. Moreover, both URLs must not contain a username or any other authentication info.
Integrations
The Integrations tab allows you to integrate XTC with your Slack Workspace to be notified of certain events like load test status changes. See the Slack Integration for further details.