Spring GDS 25th Anniversary
A logistics company that ships to 190 countries built something to ship to itself.
An edge case is a situation at the boundary of what a system expects. The empty list. The maximum length. The zero. The negative number where only positives were planned for. Software usually handles the middle of its range fine. It breaks at the extremes, and the extremes are exactly where edge cases live.
The term gets used loosely, but there's a useful distinction. An edge case pushes one input to its limit, like a search box receiving a 10,000-character string. A corner case is where two or more of those limits meet at once, like that same long string arriving in a different language while the network drops mid-request. Corner cases are rarer and harder to reproduce, which is what makes them dangerous. A date field that works all year and then fails on February 29th is a classic edge case that hides until the calendar finds it.
The reason they matter is cost. An edge case that slips through looks like nothing during a demo and then takes down checkout the one time a customer pastes an emoji into a name field. Good testing names the boundaries on purpose: minimums, maximums, empties, duplicates, and the odd inputs real people actually produce. Finding them in QA is cheap. Finding them in production is not.
We hunt edge cases instead of waiting for them. When we scope a feature, we map the boundaries early: what happens at zero, at the limit, with nothing entered, with the same thing entered twice. Those become test cases before the code is written, so the handling is designed in rather than patched in after a customer trips over it.
Some only surface through exploration. Our quality assurance pairs automated checks on the boundaries we can predict with exploratory testing for the ones we can't, where a tester pokes at the seams the way a real user eventually will. We log what we find and feed it back into the suite, so each edge case we catch becomes a check that stays caught.
Worried about the inputs nobody planned for? Let's find them before your users do.
A logistics company that ships to 190 countries built something to ship to itself.
Turning a brand into a working business.
Half a million people. One app. Zero chaos.















