Who tests their cloud code anyway?
summary
Shows concrete Azure tools and actions: use deployment slots with traffic percentage (demo of a forgotten 10/90 split), provision disposable VMs with Dev Test Labs and auto‑shutdown, run scripted load tests via Azure Load Testing or VS Code + Locust (example runs hit ~118k requests, 48 virtual users; be aware of cost), write unit tests for Azure Functions locally, use managed identities for integration checks, and run Chaos Studio experiments (deny Key Vault access for 10 minutes) to validate failure modes.
AI-written summary · about
chapters (6)
- 0:00Introduction and approach
- 14:26Managing development VMs
- 20:13Azure load testing tools
- 37:14Serverless function testing
- 45:14Chaos engineering on Azure
- 55:44Testing resources and conclusion
related talks
40mWho tests their cloud code anyway?
54mWho Tests Their Cloud Code Anyway?
48mTesting The Cloud
17mDeep dive on Azure Load Testing in CI/CD
46mLeverage Azure Testing Services to build high quality applications
06mAzure Load Testing
38mStating the Obvious: Adding Non-functional Tests to CI
34mPerformance testing: from zero to hero with k6 & Azure