The Software Potato
summary
A simple visual model calls the system the software potato: a small requirements box inside a huge blue cloud of all possible uses and a brown kernel of what actually matters; complete testing is impossible so teams combine automated unit and integration tests with exploratory testing to cover different slices. Coverage maps show dense automated checks for calculations, scattered manual exploration, and gaps filled by serendipity as skill+luck. A concrete takeaway: build learning from many sources — the presenter recommends finding about 37 sources to fill the potato.
AI-written summary · about
related talks
48mA Reflection on Software Testing
47mTangible Software Quality
43mOmg, how do I write software that isn't a ticking timebomb!?
01h 14mVisualizing Testability
37mThe Lazy Tester
29mAre you testing enough - Qt application Quality Assurance
52mNavigating Software Quality - From Chaos to Control
45mBuilding Tools to Free up Exploratory Testers