XTC v99
Load Testing
-
Whenever a load test changes state, users can be notified, currently only via Slack. Since not all users have Slack, we have started to include email as well. As a first step, you can now configure a list of custom email addresses at a load test, and this list will be notified when the load test finishes. See the new Notifications tab on the details page of a load test.
-
The REST API for load testing projects has been enhanced to allow the configuration of custom machines for a load test. This includes:
- The list of custom machines (specified as
<host-or-ip>:<port>
). - The password required to communicate with these machines.
- The number of XLT agent processes per custom machine.
- Whether to remove regular cloud machines from the load test.
For full details, see the “update” variant of the action endpoint.
- The list of custom machines (specified as
-
Previously, XTC used a mirror of Maven Central provided by Google when resolving dependencies for your load testing projects. As this mirror seems to be no longer maintained, XTC now points directly to Maven Central.
-
Currently available XLT execution environments:
- XLT 8.x → 8.6.0 (deprecated, will be retired in July, 2025)
- XLT 9.x → 9.0.0 (migration needed)
Monitoring
- On the Dashboard and the History pages, the colors used to represent the different states of a scenario execution have been made consistent across charts, tiles, and icons.
- Quality sensors can be configured to trigger a notification when a scenario execution is forcibly aborted by the system because it exceeds the maximum allowed runtime. Use the new General - Execution Aborted metric.
Platform
- Minor UI improvements.