Variations During Testing
summary
A concrete claim: repeating the same happy-path checks proves intended behavior but misses real‑world risks, so deliberately vary inputs and actions to uncover them. Recreate the money‑transfer scenario with timed distractions and session inactivity lockouts, use persona‑based testing (elderly slow reader, social multitasker, malicious user), and vary device state (low battery, full storage, dark mode) and app switching; automate repetitive checks and do exploratory sessions that simulate interruptions to find surprising bugs.
AI-written summary · about
related talks
41mSheekha Singh: You cannot TEST everything
08m"Test Repeatability"
44mExploratory Testing - MobTesting, BugBashing, CrowdTesting, Oh, My!
59m.NET Testing Techniques You Didn’t Know You Needed
26mTesting the Tricky Stuff
51mAutomating to augment testing
01h 19mYou Can't Test This? Hammertime!
57mAdvanced Testing Techniques: Tips from the trenches