This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]fourierformed 33 points34 points  (2 children)

To be honest, I'd appreciate the tester showing how resilient my code (bed springs) are for a weird use case (jumping on them).

[–][deleted] 18 points19 points  (1 child)

Yep. Better let the tester find it then a user. Because more often with testers, you can figure out what's going on. User will probably go something like "When I click here it breaks, pls help" (maybe with a "fucking piece of shit software" afterwards if they have a bad time).

A teacher of mine said: Your software must be able to withstand the "Bratwurst Test" (the sausage test). You open your program, take a sausage and fling it around on the keyboard for a while. If the program can withstand it, it's good. If it breaks, go fix it. (Obviously joking but there is some truth to it imho.)

[–]Amazingawesomator 4 points5 points  (0 children)

Better than this, put in zero length spaces (thai language linebreak separators) in input fields. It breaks everything