“Absolutes in language and how they apply to Software Testing"
summary
Argues that absolute words like must, never and should blind testing and gives concrete examples: automate through the API versus GUI, do not use cucumber for automated gui testing, and a requirements example of a six‑character password where testers actually try five, zero, empty and null inputs and different browsers. Recommends writing down personal absolutes, listing the “because” reasons that make them biases, and deliberately generating contextual variations or quick checks when recent regression evidence justifies skipping fuller exploration.
AI-written summary · about
chapters (6)
- 0:00Absolutes in language, and how they apply to software testing.
- 0:20Do not use Cucumber for Automated GUI Testing
- 1:56Context Helps Us Test
- 3:51Testing has the job of exploring certainty and revealing its limits.
- 5:12Explore Your Beliefs
- 6:08You may have good reasons for holding a bias. Identify what they are.
related talks
01h 48mNo Such Thing as Manual Testing and Other Confusions
28mYour Testing Strategy is broken - lets fix it!
53mTesting without dogma
41mNo Such Thing as Manual Testing and Other Confusions
07m"The Problem With Testing"
33mMore Than Automation: How Good Acceptance Test Can Make Your Team Happier
48mA Reflection on Software Testing
24mEVERYTHING YOU MUST KNOW ABOUT AGILE TESTERS