Improve continuous delivery by target quality aspects by your tests
summary
Argues CI/CD should measure and build confidence not test count, and prescribes breaking quality into functional, operational, strategic aspects then choosing tests to prove those specific risks. Shows a concrete example (patient‑management): verify anonymous informational pages and timezones, mobile and multilanguage UX, regulatory handling and scalability. Recommends collaborative mapping with system/component diagrams and the automation pyramid and testing quadrants to select targeted unit, integration and UI tests that actually give deployable confidence.
AI-written summary · about
chapters (6)
- 0:00Introduction and speaker background
- 2:57Challenges in continuous delivery
- 6:56Focus on confidence over tests
- 9:23Quality aspects breakdown
- 12:56Defining quality goals per project
- 14:43Building a testing strategy
related talks
20mEnsuring Quality in DevOps Culture
22mTest Automation and Beyond: Implementing Continuous Testing Effectively
19mBusiness Impact Delivery Using Test Automation
20mThe Road to Continuous Testing
42mIntroducing the benefits of the testing diamond
50mThe End of Testing as We Know It
35mBetter, Faster, Stronger - Delivering High Quality Products
31mQuality Engineering mindset and TBS