Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2024 Poal.co

233

Orders a beer. Quickly orders a second beer before the first is served. Orders 0 beers. Orders 999999 beers. Orders a lizard. Orders -1 beers. Orders a dsfsdfsd. Orders a DROP TABLE.

The bar's first real customer walks in...  asks where the bathroom is. The bar bursts into flames killing everyone.

Orders a beer. Quickly orders a second beer before the first is served. Orders 0 beers. Orders 999999 beers. Orders a lizard. Orders -1 beers. Orders a dsfsdfsd. Orders a DROP TABLE. The bar's first real customer walks in...  asks where the bathroom is. The bar bursts into flames killing everyone.

(post is archived)

You are currently inside a comment thread.
Click here to see all the comments (19).
[–] • 0 pt

Ok, I'll spoil it. The joke is that QA engineers are supposed to test all the edge cases. Rarely do they do a complete test. As the joke illustrates, no one considered a very common user case of a customer asking where the bathroom was. The code then crashes.

In software, this occurs way too often. Programmers see a very narrow scope of use cases and so do the QA testers.

[–] [deleted] • 1 pt

He's right, although to me the funny part is that the guy orders all the invalids, because he cant help but fiddle with things.

At least thats how it works for me lol.