How I lost my QA job
summary
Team shifts QA into development ownership, adopts Continuous Delivery and TDD, and builds devops pipelines, code-review checklists and pair-programming coaching to enforce tests. Automated Java tests grow from 5,000→12,000 tests and measured coverage climbs 68%→80% over about six to ten months, while heavy Selenium suites shrink to roughly ten stable end-to-end checks. Result: testers move to infra or product roles, manual UI checks fall to developers, and releases get faster but require upfront training, expert mentoring and active tracking to succeed.
AI-written summary · about
chapters (11)
- 0:00Introduction and background
- 5:10Starting TDD adoption process
- 10:51Challenges in TDD implementation
- 14:45Key lessons from TDD transition
- 20:12Quality assurance without QA engineers
- 27:20Testing as part of development
- 31:35Q&A session begins
- 33:56TDD results and team impact
- 39:48Metrics and bug tracking
- 43:20Role of QA engineers today
- 48:51Future of testing in large teams
related talks
36mWhy a Growing Company Needs a Growing QA Team
27mProfessional Growth of the QA Engineer in Start-Up
45mWhat Would You Say You Do Here? Reframing Your Role In The QA Field
14m5 Challenges I Faced As A New QA Lead
37mDavy Kenis: QA No More: Revolutionizing Software testing
47mQA 3.0. New Generation
58mHow I became a tester!
24mAs a Computer Science university student, how did I become a trusted tester...?