Thinking of Quality as developer productivity tool
summary
Argues that quality engineering becomes a developer productivity tool by shipping concrete practices: publish test plans before development, add API contract and a boilerplate that asserts 200/400/500 responses, and integrate test management with Jira so devs run tests without context switching. Recommends tools like Postman, SonarQube for unit test coverage, visual validation and CI/CD pipelines, and contract testing; cites that orgs who engineer quality into SDLC are more than 50% likely to ship better software and to cut MTTR and release time when tracked with DORA metrics.
AI-written summary · about
chapters (8)
- 0:00Introduction to talk
- 1:02QA as development blocker myth
- 3:09Quality as productivity enhancer
- 6:15Quality coaching strategies
- 8:45Standardized repeatable processes
- 10:28Quality tooling for developers
- 12:55Measuring quality impact
- 13:16Conclusion and key takeaways
related talks
28mInstilling the built-in quality mindset into a dev team
35mWhy Software Engineers Should Make Quality a Priority
46mQuality Engineering for DevOps Teams
20mEnsuring Quality in DevOps Culture
13mCommitting to quality
49mIs your Quality on the Road to Nowhere?
53mEssential Tools for Improving Test Code Quality
21mImproving Quality Through Effective Communication Between Tester and Developer