Stating the Obvious: Adding Non-functional Tests to CI
summary
Adds concrete CI steps: a VSTS build for a simple ASP.NET Core app on Azure that uploads a load script and runs a smoke test 1 minute 25 users during release, or a longer 50‑minute run that ramps to 500 users to validate latency, throughput and error rate. Uses Visual Studio load tooling (and mentions JMeter/blazemeter alternatives), correlates load generators with monitoring, and surfaces real failures like DB connection‑pool exhaustion and bad connection strings discovered before production.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:41Agenda
- 3:10Why It Is Obvious To Add the Performance Testing to Your Pipeline
- 19:44The Load Testing Script
- 22:26Consideration for C Icd
- 29:59Error Rate
- 35:30Performance Testing Is Never Done
related talks
17mDeep dive on Azure Load Testing in CI/CD
58mWho tests their cloud code anyway?
40mWho tests their cloud code anyway?
01h 02m1,2,3… testing: is this thing on(line)? Meet your new Microsoft Testing tools
54mWho Tests Their Cloud Code Anyway?
45mTesting Your Web Apps
48mTesting The Cloud
34mPerformance testing: from zero to hero with k6 & Azure