Are we Quality Assurance or Testers?
summary
Argues that QA and testing are different: QA designs processes to prevent defects while testing is a quality‑control activity that finds defects. Cites a 300‑engineer company with about 50 testers, uses metrics and audits, reviews, inspections, demos and automation for prevention and detection, and advocates shift left and continuous testing. Gives concrete failures: 2,000 French trains built that don’t fit ~1,300 stations (out of ~8,400), and a title‑change experiment that opens meeting doors but only partly changes outcomes.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:51ning business ideas into extraordinary digital products. Fast.
- 5:26Testing or quality assurance
- 12:33Quality Control
- 15:16quality assurance and testing
- 24:05If we want to be serious about quality, it is time to get tired of finding bugs and start preventing their happening in the first place.
- 31:11ambassador engineer test ninja quality analyst tester
related talks
51mQuality Assurance vs. Testing
35mTesting != Quality
53mIs having a QA a symptom of a dysfunctional team?
10mQuality Assistance vs Quality Assurance
09m"The Tester’s Role: Balancing Technical Acumen and User Advocacy"
46mWhat can QA do and what should it not fear?
06mDoes QA have a place in DevOps? Heck yeah!
30mHow a Tester Can Survive in an Agile Environment