Sheekha Singh: You cannot TEST everything

on YouTube ↗41m

" summary

Claim: exhaustive testing is impossible and 100% coverage still misses real users' behavior. Gives a concrete P1: an account nickname containing an emoji crashes the app despite extensive unit and automation suites. Recommends a shift to continuous exploratory testing, risk-based test plans that mark out-of-scope items, concise bug reports, and team-wide ownership of quality. Shows how to measure value beyond bug counts, stay calm during releases, document odd cases, and add targeted tests after production failures.

AI-written summary · about

" chapters (7)

1. 0:00Introduction
2. 3:01QA work reality
3. 13:09Favorite production bug
4. 19:52Exploratory testing
5. 23:50Mindset shifts in releases
6. 32:53Testing improvement
7. 35:25Q&A

" related talks

• 30m"Timbits"Paul Holland, Tim Coulter · CAST 2014
• 08mVariations During TestingLavanya Mohan · TestFlix 2022
• 23mWhy testing is also a developer's problemBlake Reynolds, Eric Hastie · droidcon New York 2024
• 24mThe more we test, the worse?Pongpipat Kawlerk, Xudong Yang · XConf Thailand 2023
• 49mThe Secret to Successful TestingJohan Jonasson · QA Fest 2018
• 20mPanel Discussion on TestingTomasz Łakomy, Kent C. Dodds, Iris Schaffer, Sophie Au · React Summit 2020
• 28mYour Testing Strategy is broken - lets fix it!Luise Freese · WeAreDevelopers World Congress 2025
• 53mLife of a Tester: From Once UponJennifer Bonine, Janna Loeffler · HUSTEF 2019