Azure App Testing (Azure Load Testing)

Visit Website

Introduction

Microsoft now brands its managed load-testing service as Azure App Testing. It combines Azure Load Testing, which runs Apache JMeter and Locust tests at cloud scale, with Playwright Workspaces for running Playwright end-to-end tests in the cloud.

For load testing, you upload a JMeter or Locust script (or create a quick URL-based test), choose engine instances and see client-side metrics alongside Azure resource metrics.

Features

1. JMeter and Locust: Run existing scripts at scale.
2. Quick tests: Create URL-based tests without a script.
3. Azure metrics correlation: See server-side metrics from Azure resources.
4. CI/CD: Run from Azure Pipelines and GitHub Actions.
5. Playwright Workspaces: Cloud browsers for Playwright tests.

Pros

Cons

1. Azure-centric: Best value when your app runs on Azure.
2. Usage pricing: Costs depend on virtual user hours; check the calculator.

Usage and Links (Example)

Create an Azure Load Testing resource in the portal, upload a JMeter .jmx or Locust script, set engine instances and run. For CI, use the Azure Load Testing GitHub Action or Azure Pipelines task.

Resources:

• Azure App Testing (Azure Load Testing) website
• Pricing

Pricing

Pricing is usage-based (virtual user hours for load testing; test minutes for Playwright Workspaces, which has a 30-day free trial with the first 100 test minutes). See the Azure App Testing pricing page for rates.

Recommended for?

1. Azure teams reusing JMeter or Locust scripts.
2. Teams wanting load and browser testing in one Azure service.
3. Not a fit for teams avoiding cloud lock-in.

Conclusion

Azure App Testing offers managed JMeter/Locust load testing and Playwright Workspaces under one Azure service.