Breaking the build with K6 load tests
summary
Shows how to write JavaScript k6 scripts, run them with the k6 CLI, and wire checks plus thresholds into an Azure DevOps YAML step so the build fails when performance regresses. Demonstrates stages that ramp to 100 virtual users, observes average requests/sec and a max latency near four seconds, and proves thresholds can abort the test and break the pipeline. Notes not to run heavy tests on build agents and suggests k6 Cloud or separate deployment slots.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:06Load Testing Tool K6
- 2:58Duration Views
- 4:41Checks
- 5:15Http Get
- 6:28Thresholds
- 8:52Stages
- 10:34How To Run Azure Pipeline with the K6 Tests
related talks
34mPerformance testing: from zero to hero with k6 & Azure
55mPerformance Testing From Zero to Hero with K6 & Azure
34mK8s load testing at scale with k6-operator
45mDistributed load testing with k6
26mTo see what others can not... You must climb the mountain, A Introduction to Load Testing
43mEmergent Load Testing Rules for Organized Chaos
01h 01mBreaking your REST APIs to make them stronger!!
46mDistributed load testing with k6