3 ms·
A QA engineer walks into a bar
- ImPostingOnHN 3y agohttps://nitter.net/brenankeller/status/1068615953989087232 https://nitter.net/brenankeller/status/1068615953989087232
- stoneman24 3y agoYes, 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.
- AdmiralAsshat 3y agoThe 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.
- philk10 3y agoTrue 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.)
- stavros 3y agoNo, 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.
- M95D 3y agoThe problem is, most of the time, they already paid...
- baal80spam 3y agoIs this suggesting that QA focuses on non-realistic scenarios forgetting about the practical and real world use cases?
- drewcoo 3y agoOr 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)?
- michaelt 3y agoI 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.
- Gunax 3y agoI 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.
- revskill 3y agoYou mean "The blue screen of death" ?
- wslh 3y agoDoes someone has real references about the story mentioned in that thread: https://nitter.net/pic/orig/media%2FDtaxv7OXQAEJ8jZ.jpg https://nitter.net/pic/orig/media%2FDtaxv7OXQAEJ8jZ.jpg (I tried to search that but was difficult for me to find it)
- philk10 3y agoQA isn't doing testing, a QA engineer might ask why the tester is testing those scenarios...
- asylteltine 3y agoPlease don’t post twitter links. Use a screenshot or nitter
- spamatica 3y agoAs 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 https://news.ycombinator.com/item?id=24339298
- eesmith 3y agoFrom [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.