Making your tests visible: displaying relevant test metrics in your projects
summary
Shows concrete metrics and controls: capture service response times and raise warnings for 50%+ regressions, run end-to-end performance journeys (search→select→checkout) and alert when journey time jumps from ~15s to ~20s, wire monitors to show unique production defects by module, run OWASP checks and break the build on high-risk security findings, use sonar tube for code smells and cyclomatic metrics, parallelize suites to hit a ~10 minute regression target, and auto-report trend spikes so teams own fixes.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 2:52Why should we care
- 4:25Share the pain
- 7:10Check production
- 8:00Improve ownership
- 10:11Prevent issues
- 11:25Make sense of it
- 11:58Performance measurements
- 13:35Warning messages
- 18:30Security
- 20:50Quality metrics
- 23:38Code quality metrics
- 25:51Enduser functional tests
- 28:49Defects
- 29:38Confidence
- 30:32Unique defects
- 32:19Have a look at them
- 33:10Build failures
- 35:36Aphorism
- 36:57Questions
related talks
41mThe Tester’s Guide to Quality
40mWhy component level performance testing should always be part of CD and CI
53mTransforming testing methodologies: From manual to robust strategies
31mMeasure it or it didnt happen
53mEarly Performance Testing: Finding News You Can Use
43mTo Measure or Not to Measure? That Is the Question
40mAutomated Performance Testing In Preproduction
33mTesting Your Testing Strategy