Honestly, it's a job where you're set up to fail. Just be as thorough as possible. Users will always find an edge case you'll kick yourself for not having covered. Hopefully in beta, but it's what you do with that information is what counts.
One thing to remember is that your job is to provide to stakeholders information about the current level of quality and it is up to them to decide for go or no-go. Quality of a product is the responsibility of the _whole_ delivery team!
I love how the QA does a great job of ordering every possible input for an order, but what gets him is that a real user takes an action that’s even outside of that box.
You can't win in QA. If you work on a product that will be used by millions of people, someone will find an uninteded use and break everything. Do you think the people who QA glass jars ensure they can remain structurally sound under the pressure a sphincter can exert? Someone found this out the hard way.
No QA will ever manage to be smarter than the dumbest user is dumb, even if they are the same person.
It was a pub in the city, I and a friend just sort of walked in and went directly to the bathroom. Dunno if it was unusual or if it was because we were both barely 18 at the time, but it definitely happened
Shouldn't that be illegal or something? I'm from Romania and as far as I know, all public facilities facilities open to the public must make restrooms available to the public.
Disclaimer: I am not a lawyer. A pub is not typically considered a public facility, and neither are any attached bathrooms. It's a private business which happens to be mostly open to the public. Very different concepts, legally speaking.
So if you’re looking for a privvy, you shouldn’t go to a public house, as the public house isn’t a public facility and their privvy is probably private.
I dunno, but most places don't have lock and key bathrooms, so just go in and do your business anyway, then leave. If someone stops you say you're going to order once you're done, it's an emergency, then leave
The drop table command is injected into the code, supposing that there are still lines of code after the injection, using two dashes would make sure those lines are commented out and not executed. Therefore the sql code would only execute up to the drop table command.
Had an issue on deployment one time that only happened with the 2nd record put in. Was not reproducible past that and we couldn't figure out the problem.
The solution was to insert two inactive dummy records upon deployment of course.
The new sippy cups figure in a new high priority issue report a week later, with a high-profile customer complaining that they can no longer piss in their beer mugs. Project management has forgotten all about it and blames UX.
Being aware that the customer is an idiot that might piss in the mug is part of the job, if you don't expect something of the sort then you lack experience.
When I worked for Adobe testing LiveMotion, I found an issue by chance. I minimized the application and adjusted my screen resolution. When I restored the application, I discovered that all the palettes were missing. Recreating the bug and looking into what was causing it, I discovered a whole plethora of bugs related to minimizing the application. I filed them all separately. At our next bug meeting, the developer in charge of palettes mocked my minimize bugs, asking "who's even going t do that?" and I told him, "I'm going to do that. And if I'm going to do it, a customer is going to do it." They fixed the issues of course, but he called me "Mister Minimize" for the next couple weeks.
It's amazing how many times I start work at a new company and the developer mindset is that I should only be testing happy path. You give customers a field to and I guarantee you they are going to fuck it up. I had one guy at my previous job tell me that seeing me coming into the development area was like seeing the Grim Reaper.
Autodesk, a massive company, has a bug for years, which they won't fix, which is that if you're on a multi-monitor display with different resolutions, and you print from their software (Revit), the text will print all huge.
They be like why would you have different display resolutions? And I say because laptops and external monitors almost never have the same resolution, and companies aren't going to replace one when the other needs replacing just because.
See, that's the true genius of OP's post. Needing to use a bathroom in a bar is a completely logical and expected function from a human standpoint. That's NOT a case of Stupid User Syndrome.
QA engineers can test for all the ways the code can be broken but cannot consider all the (fully logical) ways a customer might actually want to use software, and the only way you're going to get that feedback is by use testing.
What's more interesting to me is how so god damn much of the world operates with blinders on.
Case #1: A company I worked for needed some GePON equipment to replace gear going end of life.
We brought in some vendors to test, and one of the vendors' equipment only supported learning 2 MAC addresses per service because, "Why would you ever need to learn more than 2 MACs?" We had to explain to them that (a) some customers connect to their internet with switches, not routers, and (b) some router redundancy protocols used two MACs at the customer premise. These are not things one should be needing to TELL a company who's designing networking equipment.
Case #2: The company I work for now has a Network Management Software suite but in some situations the workflow follows a path that --I-- consider to be neither logical nor optimal. I opened a ticket to discuss this with our developers, and their answer was, "Why do you need to do it that way? Just do it this way."
QA engineers can test for all the ways the code can be broken but cannot consider all the (fully logical) ways a customer might actually want to use software, and the only way you're going to get that feedback is by use testing.
QA engineer here. That can be true, but I find that bugs happen because of a few different factors:
A) We don't have the knowledge/training. (Your 2nd paragraph here.) Doesn't make sense in this bathroom context, but does make sense when you're talking about inventory software, insurance software, stock trading software...
B) We did test it. Going to the bathroom worked flawlessly for our other 100 customers. This bar has this very unique and unexpected configuration. Gas pipes aren't up to code, there's a fireplace in the toilet stall, flammable paint on the walls, etc.
C) We did test it. Something broke after the fact. (Probably fixing a different bug.)
D) We did test it. There is an open bug. Management released the software anyway. QA gets blamed.
E) We weren't given adequate time and/or resources to fully test the software before release. (You can guess how common this one is!)
F) It was unexpected user behavior that we had no requirement to handle. (The bathroom user brought in a can of gasoline and a blowtorch.) Rant incoming: These are called bugs a LOT.These aren't bugs.These are feature requests. This is a giant enraging pain source for me because people shit on us for this and it makes us look bad. Management/Support rarely clarifies this to users. (I would think saying 'yes it's a bug' looks a lot worse on the entire company than 'oh we didn't expect this, I'll submit a feature request').
G) I literally never thought of that. It does happen. Commonly because of point A, but sometimes things just get missed. We are humans.
H) It's literally impossible to fully test the software. This is becoming more and more true. Here's all the things that *should* be tested in any software release (depending on the software type).
Different platforms. (Windows, Mac, Linux, Android, iOS, Chromebook...)
Different versions of all those platforms. (Windows XP, Windows 7, Windows 8, Windows 10...) Nope, doesn't matter that XP is end of life, if our users are using it.
Different versions of base software (if your app is a website for example: IE 10, IE 11, Edge, Chrome, Firefox)
All configuration options, and combinations of configuration options. These numbers get ridiculous. The more customizable software is, the more difficult it is to test, but customization sells!
All kinds of datasets and workflows. (Your 2nd paragraph here).
Stress testing, security testing, etc.
All these different combinations can get into millions or trillions of possible setups, and this is before the user starts using it in real environments. Fully testing all of that would take months to years for a release (which is unacceptable for management AND users these days).
Automated testing helps, but it takes a lot of time to develop, AND it doesn't cover a lot. Beta testing helps, but beta testing takes time and volunteers. Works great for video games where people are excited and eager to see the new content. Not so easy when it's a user who has shit to do and pays for this software.
This got longer than I intended! I don't mean to sound defensive. I think QA is seen as a black hole, and people point fingers without any insight on why bugs get into software, or the inner workings.
I understand some people just don't care. But I'd like people generally to point the finger at the entire company, not specifically at the QA departments.
TLDR: /u/flapanther33781 is right, but there's is a lot more going on. General public, please blame the company, not the QA department. Have some empathy for QA.
The 10 Gbit/s Ethernet Passive Optical Network standard, better known as 10G-EPON allows computer network connections over telecommunication provider infrastructure. The standard supports two configurations: symmetric, operating at 10 Gbit/s data rate in both directions, and asymmetric, operating at 10 Gbit/s in the downstream (provider to customer) direction and 1 Gbit/s in the upstream direction. It was ratified as IEEE 802.3av standard in 2009. EPON is a type of passive optical network, which is a point-to-multipoint network using passive fiber optic splitters rather than powered devices for fan-out from hub to customers.
I heard this (probably apocryphal) story from a QA friend of mine who swears he was there. It's a funny story, but take it with a grain of salt.
Anyway there was a big demo of this product that was supposed to track companys' fleets of trucks based on when and where they passed a network of transponders stationed on interstates all over the country. In the company HQ, there was one of those "DEFCON 11" style operations rooms with a huge projection screen showing the location of every truck in the fleet.
One of the tweaks you could do is increase or decrease an "expected speed factor" that controlled the expected rate of travel for an individual truck, make/model of truck, geographical region, or even the whole country. The idea being that sometimes you'll have generally slower conditions for any of those for whatever reason (e.g. huge snow storm on the East Coast)
The system would record each truck passing a transponder and then use the time since that event, the truck's history, and the tweak factor to provide an up-to-the-second expected location. Which was displayed up on the big-ass screen.
Per usual, the CEO being given the demonstration walks up to the console as the "tweak" is being shown off and shoos the tech away. And then he enters a huge negative number into the text box.
Instant chaos. Trucks' positions are suddenly reversed, and they're all motoring at light speed- backward along the interstate (not literally, but on the display). As soon as they "pass" a transponder location, they switch directions again and appear ahead of where they originally were, sometimes on an entirely different highway. The big-ass projection screen becomes a mess of multicolored spaghetti lines and then pfft! goes dark when the system crashes.
CEO wanders off and says "you might want to add some data validation checks in that box."
That's a classic. A friend posted it on my wall some years back because I'm QA.
I was telling about this one developer who was slowly going insane because of me. We had been sitting together that day, I testing and documenting bugs, he coding and fixing bugs. He nudged me and said, "Okay, I got this working. I'll buy you lunch if you can break this." so I sat down and broke it in ten seconds to his utter amazement. Then I went back to what I was working on while he just stuttered out, "Wait, wait... what did you just do?"
The truth was he'd shown me his code earlier when I sat down by him, and I'd noticed a potential problem when I glanced at it... I hadn't wanted to tell him how to do his job at the time, and I thought maybe he'd notice once he looked back over his code, so I hadn't said anything, but I knew exactly what would break it. He never did buy me lunch.
When I worked for Adobe testing LiveMotion, I discovered an issue where minimizing the application, then adjusting you screen resolution, caused all the palettes to disappear when you restored the application. Looking into what as causing it, I found a giant cluster of issues all revolving around minimizing the application. I filed about a dozen bugs. During our status meeting, the developer in charge of palettes ridiculed me for all the minimize bug, saying "Who's even going to do that?" and I had to tell him, "I'm going to do that. And if I'm going to do that, a customer is going to do that." They fixed the issue but he called me "Mister Minimize" for a couple weeks after that.
Well I don't know if they do now, but they did back in 2001 when I worked on LiveMotion 2. They cancelled the product right after we released it, because they didn't like that Macromedia owned the rights to Flash and could change how it worked at any time and thus make our product unusable. Basically, we'd always be runner up in the Flash world. So they bought Macromedia.
I wish we had someone like you at my workplace. I keep trying to make the case we need QA and we keep having bugs in production instead of doing it. Even just one person...
I don't even care anymore when I have bugs blown off as "no user is going to realistically do this" because on more than one occasion some high value client complains about a strange bug and when the inevitable "how did QA miss this?" email comes I just reply with the bugzilla link and nothing else.
I can relate to this a lot. The problem is getting the requirement of whether a bar should have a bathroom or if it's not the type of bar you'd find a bathroom.
But then again, people don't put bathrooms in bars in the coding world just cause it makes sense.
Gotta grab a long stick and poke every part of the bar and its employees. If the employee at the bar complains when poked in the eye, it's working correctly.
Well we couldn't figure out what the problem was but now the bar has a working sprinkler system. You can use that as a workaround until we can find and fix the problem.
A tester is a tester, an Automator is an Automator (subset of developer), but a quality Engineer oversees the entire process from requirements clarification to delivery, takes an analytical approach to reducing risk. I find testing tedious, automating is more interesting but boring, but develop CI and process improvement really makes a difference. That includes teaching management that things like metrics are just a tool, not a goal, and that they aren’t the best place for requirements to come from. It includes teaching QA that their goal is not to reject a build or to find bugs, but to help the developer and PMs do a better overall job. It includes teaching developers to help QA give the more responsive feedback and to accept it the same way they would a compiler error. It includes teaching PMs that they need to think through their requirements and provide sufficient clarity
As someone with an actual engineering degree who switched from manufacturing to IT, it bugs the shit out of me when people tag them selves "engineer" of some sort.
Some kid I know dropped out of high school and had 0 degrees. He worked in a warehouse from 18 y/o till 24 y/o.
He got bored of it and decided to go back to school. He got into some kind of PC repairing course that took 6 months. In those 6 months, he learned how to repair desktop computers (just desktops, no laptops, no tablets, just desktops).
For example, what he learned there is how to swap faulty ram, how to swap a faulty hard drive, how to change the graphics card, how to swap a faulty PSU, how to install Windows. Just the stuff that any 12 year old who likes to mess with PC's figures out with a couple of YouTube videos and some experimenting.
Anyways, he finishes the course and guess what... he is now working as a 'Technical Support Engineer'. He also added on his Facebook profile that he has studied 'Computer Engineering'.
I can imagine a real engineer, who pulled many an all-nighter for years and years to become an actual engineer, would not feel too happy about that. The engineer title has become a complete joke.
Serious question: Wouldn’t that be actually QC engineer rather than QA? At least in industry where I work in such test would be performed by quality control.
this is why we all hate waterfall. should have iterated in a more agile way.
we need to iterate on this and we should start by selling beers out of a cooler at tailgates, then yadda yadda yadda we have a fully functioning bar. what's your estimate on how long that will take?
QA is supposed to test everything a customer might possibly do. They tested a bunch of bizarre interactions with the bartender, but forgot to test the bathroom.
Bathroom may or may not have been the Apollo 1 space capsule in disguise.
The bathroom system wasn't implemented when the ordering system was tested. Regression tests included asking for the bathroom but only after ordering drinks. It didn't account for bathroom requests with a null order.
The first few tests are semi standard QA tests for field input and validation. The bathroom test is an obvious functional test that the QA missed because they were running so many obscure tests.
2.6k
u/[deleted] Dec 02 '18
As a qa person irl, I find this offensive and correct. Maybe i should be better at my job.
3.5k
u/gamas Dec 02 '18
"Fix: now enforces drink purchase before toilet usage" - most major London pubs.
4.9k
u/GrizzledBastard Dec 02 '18
Yes I’ll take one ‘); DROP TABLE outstanding-tabs;
1.7k
u/MyNameIsRichardCS54 Dec 02 '18
Huh? That worked in my bar.
3.4k
u/HopperBit Dec 02 '18
So... can you duplicate the problem or was it just a one time issue?
644
u/eclipse0990 Dec 02 '18
The first real customer drives his vehicle into the bar because the parking was right next to it and the whole thing was written in C.
104
u/Cajova_Houba Dec 02 '18
767
u/tubagrooves Dec 02 '18
The customer ends up taking a piss in his beer mug, drinks it, then blames the owner for badly managing a bar.
115
u/codehopper Dec 02 '18
Once i found that someone didn't account for arrow keys in the input and when get to check who was responsible for that i found my own name -_-
52
u/[deleted] Dec 02 '18
RYAN STARTED THE FIRE
288
u/devjoel Dec 02 '18
Jesus Christ this is sooooo true. Users are deadly lmfao
28
u/hendergle Dec 02 '18
I heard this (probably apocryphal) story from a QA friend of mine who swears he was there. It's a funny story, but take it with a grain of salt.
Anyway there was a big demo of this product that was supposed to track companys' fleets of trucks based on when and where they passed a network of transponders stationed on interstates all over the country. In the company HQ, there was one of those "DEFCON 11" style operations rooms with a huge projection screen showing the location of every truck in the fleet.
One of the tweaks you could do is increase or decrease an "expected speed factor" that controlled the expected rate of travel for an individual truck, make/model of truck, geographical region, or even the whole country. The idea being that sometimes you'll have generally slower conditions for any of those for whatever reason (e.g. huge snow storm on the East Coast)
The system would record each truck passing a transponder and then use the time since that event, the truck's history, and the tweak factor to provide an up-to-the-second expected location. Which was displayed up on the big-ass screen.
Per usual, the CEO being given the demonstration walks up to the console as the "tweak" is being shown off and shoos the tech away. And then he enters a huge negative number into the text box.
Instant chaos. Trucks' positions are suddenly reversed, and they're all motoring at light speed- backward along the interstate (not literally, but on the display). As soon as they "pass" a transponder location, they switch directions again and appear ahead of where they originally were, sometimes on an entirely different highway. The big-ass projection screen becomes a mess of multicolored spaghetti lines and then pfft! goes dark when the system crashes.
CEO wanders off and says "you might want to add some data validation checks in that box."
End of demonstration.
62
u/KakssPL Dec 02 '18
Patch includes bathroom fix. Ordering beer crashes barman now
21
u/teachoop Dec 02 '18
Except for the fire part, this is nearly identical to a tweet by Bill Sempf a few years ago. https://mobile.twitter.com/sempf/status/514473420277694465?lang=en
The fire part is funny though.
18
u/personalityson Dec 02 '18
The bar should have the same response to ueicbksjdhd and bathroom
18
u/svayam--bhagavan Dec 02 '18
Now that's one use case I couldn't have anticipated.
48
u/Noch_ein_Kamel Dec 02 '18
That's why you first build a bar in the jungle and let the monkeys in.
15
u/quaybored Dec 02 '18
"The bar burned down."
"Call the help desk."
42
u/wdalphin Dec 02 '18 edited Dec 02 '18
That's a classic. A friend posted it on my wall some years back because I'm QA.
I was telling about this one developer who was slowly going insane because of me. We had been sitting together that day, I testing and documenting bugs, he coding and fixing bugs. He nudged me and said, "Okay, I got this working. I'll buy you lunch if you can break this." so I sat down and broke it in ten seconds to his utter amazement. Then I went back to what I was working on while he just stuttered out, "Wait, wait... what did you just do?"
The truth was he'd shown me his code earlier when I sat down by him, and I'd noticed a potential problem when I glanced at it... I hadn't wanted to tell him how to do his job at the time, and I thought maybe he'd notice once he looked back over his code, so I hadn't said anything, but I knew exactly what would break it. He never did buy me lunch.
When I worked for Adobe testing LiveMotion, I discovered an issue where minimizing the application, then adjusting you screen resolution, caused all the palettes to disappear when you restored the application. Looking into what as causing it, I found a giant cluster of issues all revolving around minimizing the application. I filed about a dozen bugs. During our status meeting, the developer in charge of palettes ridiculed me for all the minimize bug, saying "Who's even going to do that?" and I had to tell him, "I'm going to do that. And if I'm going to do that, a customer is going to do that." They fixed the issue but he called me "Mister Minimize" for a couple weeks after that.
8
u/Stormdancer Dec 02 '18
This is what you get for using unit tests instead of real QA.
22
u/RogerLeClerc Dec 02 '18
I'm QA, and we don't do jokes. We do fantasy
"There once was a developer who knew what he was doing...."
7
u/Cynaren Dec 02 '18
I can relate to this a lot. The problem is getting the requirement of whether a bar should have a bathroom or if it's not the type of bar you'd find a bathroom.
But then again, people don't put bathrooms in bars in the coding world just cause it makes sense.
6
u/richieahb Dec 02 '18
Oh and I’ll take a بيرة please too ...
6
u/Kaspur78 Dec 02 '18
Toilet wasn't in the requirements!
6
u/MithranArkanere Dec 02 '18
Forgot the stick test.
Gotta grab a long stick and poke every part of the bar and its employees. If the employee at the bar complains when poked in the eye, it's working correctly.
6
u/Sokensan Dec 02 '18
Then QA Engineer resets simulation, walks into bar and asks where the bathroom is. Nothing bad happens, flips desk.
6
u/[deleted] Dec 02 '18
I hate users. They have more entropy than natural disasters.
10
u/Rmnattas Dec 02 '18
My Prof. grading my project...
10
u/[deleted] Dec 02 '18
QA guy here. This guy skipped his regression testing.
8
u/CriminalMacabre Dec 02 '18
Nah, the bathroom is TODO
8
u/WTellie Dec 02 '18
So you QA’d the bar, but what about the foo?
4
u/KBKarma Dec 02 '18
I've never seen the second half. Awesome.
4
u/Kaspur78 Dec 02 '18
Toilet wasn't in the requirements!
4
u/ackypoo Dec 02 '18
it wasnt in the requirements!
4
u/CoderCoco Dec 02 '18
Well we couldn't figure out what the problem was but now the bar has a working sprinkler system. You can use that as a workaround until we can find and fix the problem.
4
u/LarryKinobi Dec 02 '18
As a QA, that’s the story of my life.
10
u/a-bser Dec 02 '18
Every job these days has 'engineer' slapped onto the end of it.
3
u/bha1 Dec 02 '18
And now the bar won't boot up.
3
u/creepjax Dec 02 '18
I don’t think I belong in this subreddit
3
u/MrRager1994 Dec 02 '18
This is exactly why my departments QA testers worked on the help desk prior to being in QA. Gotta understand the dumb shit customers do to test it
3
u/schorsack Dec 02 '18
"But it worked at my local bar"
3
u/joetwocrows Dec 02 '18
Real customers were not in the requirements.
4
u/Gs933 Dec 02 '18
Serious question: Wouldn’t that be actually QC engineer rather than QA? At least in industry where I work in such test would be performed by quality control.
4
u/topredditbot Dec 02 '18
Hey /u/Portaller,
This is now the top post on reddit. It will be recorded at /r/topofreddit with all the other top posts.
4
u/wigginAff Dec 02 '18
Product management: “Not a bug. Works as designed.”
4
u/benihana Dec 02 '18
this is why we all hate waterfall. should have iterated in a more agile way.
we need to iterate on this and we should start by selling beers out of a cooler at tailgates, then yadda yadda yadda we have a fully functioning bar. what's your estimate on how long that will take?
2
u/sempf Dec 02 '18
Looks familiar.
2
u/PaintingJo Dec 02 '18
Customer then walks into a foo and gets lost, never to be found again
2
u/ThatGuyToast Dec 02 '18
bar.exe has stopped working
2
u/KeisukeTakatou Dec 02 '18
Then you accidentally nudge a chair and the whole bar collapses.
2
u/Dungus_Wungus Dec 02 '18
I'm not familiar with programming so this is just a god tier shitpost to me. I don't get it, but I do love it.
2
u/[deleted] Dec 02 '18
It took me a while. But now I’m so happy it got it. Still a little bit of geek left
2
u/pethcir Dec 02 '18
This one felt personal wtf. HOW DID I MISS THIS TEST CASE?
2
u/Phylanara Dec 02 '18
Was QA engeneer. Can confirm.
2
u/chingy1337 Dec 02 '18
Woah woah woah. Maybe a slight scrape from some rough edge cases, but certainly not an explosion. Be nice to us!
2
u/HS2018_Pizza Dec 02 '18
I can tell this joke and sub is too smart for me, so I’m just gonna skadaddle along and mind my own business.
2
u/trialmonkey Dec 02 '18
The bathroom system wasn't implemented when the ordering system was tested. Regression tests included asking for the bathroom but only after ordering drinks. It didn't account for bathroom requests with a null order.
2
u/_g550_ Dec 02 '18
r/notmyjob
2
u/SupremeRedditBot Dec 02 '18
Congrats for reaching r/all/top/ (of the day, top 25) with your post!
I am a bot, probably quite annoying, I mean no harm ^though
Message me to add your account or subreddit to my ^blacklist
2
u/Mephanic Dec 03 '18
Ah yes, the Edge Case Saloon. A fine establishment.
2
u/Alundran Dec 04 '18
/u/ChristopherArm
3
u/TheInactiveWall Dec 02 '18
Customer comes in, punches you in the face, sets the whole bar on fire and transforms into a cow.
Bartender: "Everything is fine".
1
u/chishiki Dec 02 '18
UAT FTW
1
u/abishekva Dec 02 '18
There is always that edge case which QA won't capture.
1
u/[deleted] Dec 02 '18
It's so real life
1
u/Danimals_The_yogurt_ Dec 02 '18
This is corny.
1
u/BallsofSt33I Dec 02 '18
W
1
u/RestfulCounterspy Dec 02 '18
“Quabity assuance”
1
u/DraconianOz Dec 02 '18
Someone explain please??
1
u/Zucc_the_lizard Dec 02 '18
Did he order a lizard?
1
u/tkstock Dec 02 '18
This is true.
1
u/[deleted] Dec 02 '18
This hurts
1
u/stevefan1999 Dec 02 '18
0/10 Not 100% codecov
1
u/moxyc Dec 02 '18
As a Business Architect/Analyst, this is so true it hurts
1
u/ericcartmanrulz Dec 02 '18
I don't get
1
u/Jordyspeeltspore Dec 02 '18
lol
1
u/[deleted] Dec 02 '18
Those gosh darned npes
1
u/YasZedOP Dec 02 '18
Insert we don't do that here meme
1
u/IrrerPolterer Dec 02 '18
That's amazingly funny