Quality Assistance vs Quality Assurance
summary
Argues that teams move from QA as gatekeeping to Quality Assistance by doing concrete work: add unit-test gating on pull requests to stop regressions, replace slow fragile end-to-end suites that take 8–12 hours with targeted integration and contract tests, own the test automation framework and best practices, pick up small bug fixes to learn the codebase, and run controlled production experiments via canary deployments and feature flags to validate behavior and cut staging cost.
AI-written summary · about
related talks
51mQuality Assurance vs. Testing
22mANOTHER WAY OF QUALITY ASSURANCE: ENGINEER ROLE
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
41mQuality Transformation
34mAre we Quality Assurance or Testers?
21mEstablishing Quality Assurance in Startup environment
33mFrom Testing to Quality Assurance
15mHow we do Quality Assurance at King and How Agile Jenga Helps us With our Processes