New Rules Of Engagement For Product Quality: Testing-As-A-Service In ...
summary
Claims that testing is reengineered as Testing-as-a-Service and staffed with software engineers rather than a separate QA silo, replacing a monolithic end-to-end harness with per-service micro test harness repos. Team ships weekly via continuous delivery, removes handoffs, and reports faster release cycles and smoother hiring. The concrete result is a drastic staffing shift — a reported dev:test ratio 1:8 — plus weekly continuous delivery cadence and measurable time savings in the test phase.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:43Micro Services Architecture
- 1:13The Test Phase
- 1:58TestingAsAService
- 2:13Feature Developer vs Test Developer
- 2:44Feature Developer
- 2:59MicroTest Harness
- 3:45Speeding up release cycles
- 4:00Resource plugandplay
- 4:15Left side vs right side
- 4:31Employee morale
- 4:46Efficient hiring
- 5:01Conclusion
related talks
01h 09mScaling up with Embedded Testing
35mTesting != Quality
45mWhat Would You Say You Do Here? Reframing Your Role In The QA Field
41mQuality Transformation
22mQualityOps–Left Shift Customer Success With A Thriving Quality Engineering Ecosystem
47mHow Testing is Evolving in DevOps
51mQuality Assurance vs. Testing
56mQuality Assurance to Quality Engineering