ProgrammerHumor
pleaseTestMore
Discussion
Is it?
My QA will raise issue like, when I click button, it works.
Page loaded too fast, make sure we didn’t miss something.
Page didn't load fast enough, make sure to optimize
Page loaded precisely when it is meant to, but it's not a wizard.
A long time ago the company paid for expensive custom icons and animations for the new project.
There was a loading animation which should run while the page is loading.
They run the app locally and the load was instant.
The bug report said they could barely see the loading animation.
So I made the page load for at least a second.
They were happy.
My QA once blocked a hotfix to master because the very old systemd version their test environment had didn’t like me updating the unit file and just masked it.
Systemd requiers a daemon reload to update services
I know. Postinstall did daemon-reload.
Ok, so prove your fix works without an environment when the environment was working before your fix
Be me.
Work on a really important bug that is very delicate as it affects the entire app.
Strongly warn the QA leads that they need to be pretty thorough when testing the app due these changes, as the bug's use case works as expected but the changes impacts other areas and is probable some stuff stops working as intended.
1+ month pass with no issues found, and changes are pushed to prod.
Within 2 days a client was complaining about an entire functionality of the app not working due the changes.
I'm chew off because my changes broke prod and need to stay after hours to rush a solution.
a QA tester walks into a bar the day before it opens
he stops the bartender so that he can ask some questions about him
he inspects the tables thoroughly, and ensures they are all in good spots
he inspects the kitchen and stops the cooks from working until he is done
he has a lengthy conversation with the hostess, disturbing her admin work
he leaves, deciding that the bar is up to code.
the next day a patron walks in, trips over a misplaced chair, ends up with his reservation missing, and gets food poisoning.
the bar gets sued
[deleted]
its "the bar goes up in flames"
QA bad hahahaha /s
Well, obviously there’s a lot of context that might inform a decision.
But even though you probably shouldn’t be in trouble, it does need to get fixed, and it is your code, so you’re kind of the only one qualified to fix it unless you’re new and don’t understand enough context to put out a fix.
That’s a day before demo) tomorrow afternoon they assign to you 20 more bug tickets from backlog)))
Here's my problem. They find a bug that has NOTHING to do with my code. Not even same page or api.
Is this God Miracle ?
We didn't find the bug because you didn't tell us to test for it. I need clearer instructions next time. You can't expect me to test the entire app every time, can you?
- Last words spoken by the QA tester before his mysterious disappearance.
Thats because you have 53 bugs from the last sprint to take care of.
no new bugs
This is what heaven looks like.
Reverse the case for the QA people
If it compiles we ship 🤣🤣💀💀😭😭
It's beautiful I've looked at it for five hours now
Can't fail tests if there aren't any tests.
My QA raises bugs of extremely far fetched use case of features no one uses, only for me to find that major functionallity of the system had stopped working.
Had QA test a change, only to discover when it hit production that there was a massive flaw causing half the functionality to work. Really caused me to wonder if QA even did anything at all.
At my company when QA doesn’t find any bugs they move on to questioning legacy functionality. A few days ago a tester didn’t find any issues on one of my tickets and was pinging the PA asking whether the modal dialog should close when she clicks away from it…. It’s what every single other one in our web app does
Yup, I am more worried when things compile the first time, no bugs found the first time etc.
I was working as a QA for like 6 months just after joining my first job. It was a kidneybowel (name changed) for its IoT and E-commerce tech. I have never seen a more bitter person than that. QA lead was always asking to find bugs, and questioned us how we tested a certain functionality when we found no bugs.
Since me and another colleague were uni graduates we were given the most grunt work. Regression testing and smoke after every deployment. So in our free time we developed a sort of framework around selenium to automate this (again outside work hours, on personal devices), it takes screenshots and generates reports nearly exactly how it was expected from us. We even used a pseudo random number to add or subtract items from cart. Things were going well until we got caught.
The thing was lead wasn't mad cause we automated the regression testing, she was mad cause we open soured the code, she made us delete the repo and seized the source code. I left that project after another month.
Being a dev (building "pajeetware") is still better than being there.
37 old bugs reopened.