The Configuration of a load test project is very similar to the basic project configuration, but there are a few special settings for this project type:
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 addition to the basic repository settings which can be defined for load test projects and monitoring projects alike, there are a few additional options for load test projects concerning the compiling of the test suite:
Before a load test can be started, XTC needs to compile your load test suite. If you don’t configure a build tool, Maven will be used by default, but XTC also supports Gradle as an alternative. In any case, please make sure that your load test project contains the respective build files and verify locally that the build produces the expected results.
To configure your preferred build tool, click the editing button, select a build tool and enter additional arguments for this tool if needed. Click Save Changes to confirm.
Build Dependency Cache
Building the load test suite before the actual start of the test may take several minutes to complete. Most of that time can be attributed to the download of dependencies (XLT and other required libraries).
XTC caches the downloaded dependencies of a load test project so subsequent builds should run much faster. The cache expires automatically 14 days after the last load test was run.
If you need to discard the cache (for example due to currupted or compromised artifacts), you can do so by going to this section and clicking Discard Cache.
Default Sharing Settings
To view default sharing settings, your account must at least have the role of a tester within the project.
To edit default sharing settings, your account must at least have the role of a test manager within the project.
In Sharing, you can define a default for the share expiration time of load test results and load test reports for easier project management. Each result or report sharing will offer this time as a default (but individual expiration times may still be configured if needed). Later on, all shares that use these defaults can be either deactivated, extended, or reactivated at once when required.
We recommend using the default because if the share expiration time needs to be adjusted/prolonged, you can set the new default and it will apply to all existing shares alike. This also includes disabling these shares.
The maximum lifetime of shares is limited to 180 days.
Please note that default expiration dates for results and reports are two independently set values.
Removing All Custom Share Links
To use this feature, your account must at least have the role of a test manager within the project.
It is still possible to set individual expiration times per result and reports instead of referring to the global preset. These shares won’t be affected in any way when changing/disabling the project-wide default expiration date. To remove all custom links to reports or results, you can use the buttons Remove Custom Report Shares and Remove Custom Result Shares which you find below the default sharing settings. Both will prompt you to confirm this action, as it cannot be undone.
To view properties, your account must at least have the role of a tester within the project.
To edit properties, your account must at least have the role of a test manager within the project.
In Properties, you can globally define properties or secret properties to use for test execution.
Secret properties behave the same as regular properties. However, their values will be masked with ****** both in the load test report and in the result data set. When editing an existing secret property in the UI, its current value will be shown as ***. To redefine that setting, simply overwrite *** with the new value.
Properties configured at project level apply to all new load tests alike, while properties defined at a certain load test apply to that load test only. Load-test-level properties will overwrite project-level properties. Properties that are not set in XTC will be read from the project data.