At one point I was hired as a developer by an IT Products company which was starting a new area using (at the time) more recent technologies and programming languages, but until the thing really started going they had no significant work for me to do so I did QA for a few months (mostly automating QA).
Let’s just say that having a hacker mindset and a bit of a dastardly satisfaction in “cracking” the software is a big help in QA.
I suspect that I might have enjoyed the “managing to find a way to break somebody else’s code” part of it a bit too much.
Even more real scenario: The first real visitor isn’t even a customer but a bored teenager who says nothing at all and instead takes a piss on the floor. (Anyone who ever published anything on the internet knows this scenario.)
I once had a QA engineer file a bug saying they couldn’t do negative testing since negative numbers were converted to positive.
The function took an unsigned integer. Took a lot of explaining to get them to understand that negative testing isn’t necessarily negative numbers.
I’d argue that the system shouldn’t automatically convert negative numbers to positive numbers. Instead, it should display an error to the user. Of course, that’s an abstract thought as I don’t know what was the system and who interacted with it.
Clearly the QA should have ordered a &#%@*
With a side of ‘); DROP TABLE Orders; —
Ah, yes. Little Bobby Tables
I don’t think he’s little anymore.
I think the customer tried to pass the wrong type. Happens to us all.
Customer ate Taco Bell before going to the bar.
