Managed service generating heavy traffic, from Locust or JMeter scripts or simple URL tests, against apps wherever they're hosted. For Azure apps it also captures server metrics, and test criteria can fail a CI/CD run.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Azure Load Testing in context, with comparison tables and the common traps.
Terms in this definition
- Locust
An open-source tool, written in Python, for generating load. Besides JMeter scripts, Azure Load Testing accepts Locust ones (testType: Locust).
- URL
The web address of a resource, on which URL-based routing relies.
- CI/CD
Pipelines, for example in Azure Pipelines or GitHub Actions, that build, test and deploy code automatically; short for continuous integration and continuous delivery.
Related terms
- Apache JMeter
An open-source tool for load testing. Azure Load Testing runs its JMX scripts with support for every JMeter protocol and plugin, and also supports Locust.
- JMX
Apache JMeter saves test plans in this format. Azure Load Testing can run such scripts, with any JMeter protocol or plugin, by setting testType to JMX; it also handles Locust and URL-based tests.
- Load Test Contributor
Grants permission to see, set up, change and launch Azure Load Testing tests and runs. A pipeline's identity needs this built-in role before it can carry out load testing.