Deep dive on Azure Load Testing in CI/CD
summary
Azure Load Testing runs JMeter scripts from CI/CD (GitHub Actions) with secrets pulled from Key Vault and test configuration in config.yaml; it enforces SLIs such as error rate <=10% and 90th percentile <=100 ms (landing page example 3,000 ms). A demo e‑commerce run uploads results as GitHub artifacts, fails two of three SLIs, and surfaces server bottlenecks — Cosmos DB RU hits 100% and product SQL CPU reaches 100% — so the test exposes where to scale or tune.
AI-written summary · about
chapters (8)
- 0:00Introduction to Azure Load
- 1:33Application demonstration
- 2:20Configuring JMeter scripts
- 4:40Setting up test resources
- 6:00CI/CD pipeline integration
- 11:09Analyzing pipeline results
- 12:36Diagnosing bottlenecks
- 15:32Conclusion and resources
related talks
45mContinuous Load Testing with GitHub Actions
34mStress-Test tools in Azure to optimize your reliability
06mAzure Load Testing
29mAzure Load Testing in action
58mWho tests their cloud code anyway?
48mTesting The Cloud
40mWho tests their cloud code anyway?
55mPerformance Testing From Zero to Hero with K6 & Azure