Not Fake News, Dev QE collaboration is possible
summary
A five‑year effort yields concrete practices: developers build an automated tiered zero testing (lmst) suite that runs in about one day on four machines, flags ~5% performance dips and prevents bad patches from reaching mainline, and QE builds a continuously running network‑manager tester covering ~90% of code. A CI gate that blocks regressions shrinks day‑one blockers, an MVP release checklist coordinates testing, hardware is shared, and four to five QE staff move into development and succeed.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:28Networking
- 1:07Collaboration
- 2:42Quality Assurance
- 3:49Failure
- 4:07Serious stuff
- 4:32How did we do that
- 5:02The journey
- 5:33Unit testing
- 8:51Automated tests
- 11:15Network manager testing
- 11:41TCP stack changes
- 12:20Test plans
- 15:05Bottom line
- 16:09Share hardware
- 17:56Hiring
- 18:25Advice
related talks
36mHow programmers & testers can be productive
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
49mPanel Discussion: QE at Enterprise Scale - What Will a QE Org Look Like in 2027?
47mPanel Discussion: Who Tests the Machines? QE Leaders on Quality in the Age of AI-Written Code
01h 09mScaling up with Embedded Testing
53mWhat Happens When Everyone is QA? And I Mean Everyone!
43mLean QA: Automation, Monitoring, Experiments
12mConvergent Quality Engineering