Yes, the simplest checks always lead to a stack of bug reports that I (with my testing hat on) can generate on the developers. In addition, tab order when entering the data by keyboard. The developers just assume that the user knows as much as they know and will work in the same way as they do.
We have wide range of clients from very technically sophisticated down to people who need guidance and hand-holding. QA, for me, is ensuring all clients have a good experience with the software and get value from our software.
True story - I worked at a company where I got an angry email from the CEO telling me that 'agile was about giving the program a quick look over, our customers are better at finding bugs than we are'
( which was true only because but they didn't want to put any effort into finding bugs before release.)
Or is it suggesting that bad bathroom query code went to production even though the bathroom query story is still clearly on the backlog (otherwise it would have the usual boundary checks)?
I figured it was more of a 'none of us are without sin' type of idea - that no matter how thoroughly you cover the problems you can think of, you should have the modesty to realise there could be innumerable problems you didn't think of.
16 comments
[ 2.9 ms ] story [ 38.7 ms ] threadWe have wide range of clients from very technically sophisticated down to people who need guidance and hand-holding. QA, for me, is ensuring all clients have a good experience with the software and get value from our software.
( which was true only because but they didn't want to put any effort into finding bugs before release.)
The problem is that, unlike QA, the customers sometimes stop paying you when they discover bugs.
QA did a good job testing inputs to the orderBeer function. But they forgot to examine the other functions.
https://news.ycombinator.com/item?id=24339298