Load Test Settings
The Settings tab contains all settings for the test run. Some of these are mandatory, you need to set them before the test run can be started.
Please note that none of the test settings can be edited after the test was started.
To edit test settings, your account must at least have the role of a tester within the project.
To view test settings, your account must at least have the role of a reviewer within the project.
Under Load Profile you can override the settings in your test suite for the test properties file to be used. In addition to that, you can override the settings for test duration and load factor. All other settings, for example, ramp-up times, are not directly configurable in the UI yet, but are still read from the properties files in your test suite.
The load profile settings are only needed if you want to override your test suite settings for some reason, e.g. quickly changing the test duration or load factor without pushing changes to the repository, or switching between your prepared test property files. If the fields are left empty, the settings in the test suite will be used.
Learn more in our Load Testing section about configuring load profiles for your test run.
The most important (and mandatory) part of the test setup is the configuration of the test machines to be used.
In Common Machine Configuration you can enter a password for the communication between the master and all agent machines (a random password will be generated by default).
The machines to be used can be entered in Google Machines or Custom Machines (or you use a combination of both).
If you want to use machines in the Google Cloud, you just enter configuration details and the selected machines will automatically be started prior to the load test and terminated afterwards by XTC. To edit the Google Cloud machine configuration, click the editing button next to the Google Machines headline. There you can
- specify which regions the machines should run in (you can pick several, the machines will be spread over the selected regions as evenly as possible),
- pick an instance template for your machines (currently tiny, small, medium or xlarge), depending on how much computing power you think you’ll need,
- select the number of machine instances to start (instance count), and
- select the number of agents per instance.
Instead of starting and terminating Google Machines per XTC, you can also use other machines for testing. You can define these in Custom Machines: just enter a list of host names and the agents per instance for your machines, and make sure these are running while the test is executed.
As test sizing is a whole topic in itself, you might want to check the CPU usage after your test and maybe adjust the number of machines for the next test run.
In Properties and Secret Properties you may overwrite properties for test execution. If nothing is set here, the properties from the project repository will be used. Properties may also be overwritten globally for all load tests of this project in the project configuration.
Under Repository you can enter a branch of the project repository to be used for this test run. This is only necessary if you want to use another branch than the one you configured for the project. If this is left empty, the project or default branch will be used.