Why Software Engineers Should Make Quality a Priority
summary
Argues that shifting tests and quality gates left prevents last-minute bugs by running checks earlier and automating architecture checks; recommends adding pre-push hooks, PR jobs for unit/component tests, static analysis and visual regression, and deploying test artifacts to run journey tests; introduces accessibility fitness functions and observability alerts for cross-cutting qualities; advises one incremental change, measure impact on deploy frequency, lead time, MTTR and change-failure rate, and use quick kickoff/desk-check agreements.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:29Alice's team accessibility bug
- 7:28Earlier automated testing
- 11:39Shared accountability feedback
- 16:53Architecture accessibility
- 22:11Shift-left testing adoption
- 26:06Building quality culture
- 28:57Q&A
related talks
19mHow can we improve quality on a project?
14mThinking of Quality as developer productivity tool
20mEnsuring Quality in DevOps Culture
28mInstilling the built-in quality mindset into a dev team
31mQuality Engineering mindset and TBS
46mQuality Engineering for DevOps Teams
09m"The Tester’s Role: Balancing Technical Acumen and User Advocacy"
46mPanel Discussion: Quality Engineering - an Evolution of Software Quality as a Team Responsibility