Azure Load Testing
Produit
A fully managed cloud service that generates high-scale load against applications to test performance and capacity.
Description
Azure Load Testing is a fully managed, cloud-based service that generates high-scale load against applications, wherever they are hosted. Developers, testers and QA engineers use it to assess performance, scalability and capacity.
A simple test can be created from a URL, and the service writes the test script. For more complex cases, such as multi-request flows, non-HTTP endpoints or parameterized data, you upload Apache JMeter or Locust scripts. Test engines simulate large numbers of virtual users, and you choose how many engines to use. You can define fail criteria such as average response time, and tests stop automatically on certain errors. A live dashboard shows client-side metrics, runs are stored for comparison and tests can run from Azure Pipelines, GitHub Actions or the Azure CLI. Targets inside a virtual network or on premises can be tested too.
For apps hosted in Azure, it combines client-side metrics with server-side metrics from Azure Monitor, including Application Insights and Container insights, to show bottlenecks. Typical targets are web apps, REST APIs and databases through JDBC. The page shows no retirement or rename notice.
| Type | Produit |
|---|---|
| Documentation | learn.microsoft.com/en-us/azure/app-testing/load-testing/overview-what-is-azure-load-testing |
Part of
- Microsoft Azure · Plateforme
Developed by
- Microsoft · Organisation
Is a
- Microsoft tool · Catégorie
- Developer tool · Catégorie
Related to
- Azure Monitor · Produit
- Application Insights · Produit
- GitHub Actions · Produit
- Azure DevOps · Produit
- Azure Chaos Studio · Produit
Community wiki
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts et entreprises pour ce sujet
Personne n'a encore indiqué ce sujet. Ajoutez-le à votre profil.
Sources
Maintenu par Mirko Peters (Microsoft MVP) · Dernière mise à jour: