A QA engineer walks into a bar | Hacker News Reader

A QA engineer walks into a bar

twitter.com

34 pointsksec16 comments

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.

The QA Engineer is fired when the management insists that the regular patrons will naturally shake out all the flaws with the bar's order system.

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.)

No, it's very true that the customers are better at finding bugs than QA is, because there are more customers and they try a ton more weird crap.

The problem is that, unlike QA, the customers sometimes stop paying you when they discover bugs.

The problem is, most of the time, they already paid...

https://nitter.net/brenankeller/status/1068615953989087232

Does someone has real references about the story mentioned in that thread: https://nitter.net/pic/orig/media%2FDtaxv7OXQAEJ8jZ.jpg (I tried to search that but was difficult for me to find it)

From [2018]. I mention it because I thought someone was reposting text I read years ago, only to figure out that this was the years-ago source.

Is this suggesting that QA focuses on non-realistic scenarios forgetting about the practical and real world use cases?

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.

I take it that it's very difficult to anticipate the scenarios to test.

QA did a good job testing inputs to the orderBeer function. But they forgot to examine the other functions.

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)?

QA isn't doing testing, a QA engineer might ask why the tester is testing those scenarios...

You mean "The blue screen of death" ?

Please don’t post twitter links. Use a screenshot or nitter

As I wasn't in the know (though I can guess), I did some googling as to why and found this old thread:

https://news.ycombinator.com/item?id=24339298

Reply on news.ycombinator.com