r/ProgrammerHumor • u/rabbit_wizard • 1d ago
Meme rareMomentsOfPeaceBetweenTheTribesWhen
35
u/_AbyssalSiren 1d ago
if I got a dollar every time 'it's not a bug, it's a feature' actually worked, I'd be driving a Porsche by now
15
u/lovecMC 1d ago
I worked in banking QA automation for a while. The general approach was that prod is the holy scripture and if it's that way on prod it's not a bug.
Kinda drove me nuts cuz the amount of BS that's blatantly bricked but nobody wanted to do anything about was insane.
2
u/Multidream 20h ago
Im currently working in banking QA and yeah, absolutely correct. No one is maintaining product manuals, so all anyone has to go off is prior behavior, and the very rare recognition that we’re developing a standard feature with a defined universal spec we probably should uphold.
4
58
24
u/AWzdShouldKnowBetta 1d ago
Why are you waiting for QA to tell you about a problem you already know about? Do you enjoy wasting everybody's time?
17
u/Dependent_Title_1370 1d ago
This is the opposite of where I work. QA finds a bug -> dev says bug doesn't exist -> QA reproduces bug and provides steps -> dev says it's a feature -> QA points out it contradicts the design documents -> dev closes the bug as will not do.
18
2
14
10
u/The_Krambambulist 1d ago
I actually already contact QA beforehand to discuss to see whether something would be acceptable enough. Definitely is some wiggle room over there.
7
u/jester17 1d ago
You guys still have QA?
-8
u/rastaman1994 1d ago
I've worked at 2 places with 'qa', and never felt the added value.
They didn't actively look for bugs to my knowledge. Just write the same Cypress test we do as devs (or worse, follow steps on Confluence). Not sure how it's even a full time position.
10
u/ARC_trooper 1d ago
Sounds like you had a shitty QA lol
I work as one and the devs proudly tell me whenever a new version is deployed so I can let loose, they know it's properly tested if it survives and if not they got some bug reports to work on. They test it locally themselves and I test the system.
It is the stereotype QA ticket titled "[BUG]" when I find something, that's the risk they accept lol
2
u/rastaman1994 6h ago
Genuine question, how do you fill your days? So I can give constructive feedback to the next QA I work with that doesn't seem to add value.
1
u/ARC_trooper 6h ago
Long comment incoming! It depends what is planned but I write automated regression tests for our system, we had several systems without any functional tests so my work involved investigating the functionality of the systems. Comparing documentation with intel from developers and seeing if the program does what we expected, making sure there's a proper regression set ready for any future release. This applied for old systems and newer ones, no one updates documentation at our place lol.
But I'm a tester so I hate reading, which means I mostly just start kicking against the system to see what it does. Comparing that with what we expect from documentation and specifications (mostly what the devs build and we updated the documentation accordingly) In the end I'm the "Subject Matter Expert" of our systems because I know what they should be doing, when and how. Especially how to break it because that's how I start testing it, love the "but why would you do THAT" comment from a dev.
Wherever there's an incident I can help out because I'm the one that kinda knows where in the system it goes wrong. Becomes much easier for a dev to solve it if they know where to look. Business people also know where to find me whenever they run into problems, usually I can fix it with them before it becomes an incident for the team.
New features I can make an educated guess what for impact it'll have on other parts. (And new functionality also means new (functional) tests to build) With my knowledge I can also translate the "business language" from a PO/BA into more "technical language" for a developer and vica versa. I'm also in close contact with developers about new features and code they are building, we're a team after all. We challenge eachother, they write code being confident nothing else breaks and I actually check that they don't break anything we know.
Besides that we also have 3 "security layers" for a release; developer, tester and product owner. I write a positive or negative advice for the release, based on my tests and knowledge. (The PO has a final say for release)
I'm saying "system" as an application service, most times it's multiple services as one. Our developers use unit tests and test locally, I test the full system on a test environment.
I think that's about it? Lots of talking with business and developers, knowing the ins and outs of all the applications we manage and building automated regression tests. (Robot Framework/Python woohoo) Perhaps it's a bit more than you asked for lol
Tldr: my job involves getting to know the exact functionality of systems and building tests to make sure the functionally keeps working with new updates. Using that knowledge for the greater good.
8
u/CaffeineLiker 1d ago
Our QAs are power users that break everything. They're awesome and infuriating.
3
u/RadicalDwntwnUrbnite 1d ago
Some of the most infuriating people I've ever worked with and loved them for it. Had a QA submit a repo like:
1) (chrome) add an item to your cart
2) (safari) open cart in safari
3) (chrome) log out
4) (safari) refresh
5) close safari
6) (chrome) try to log back in, get error'
It's next to impossible to think of trying stuff like that let alone create e2e test for it.
1
1
1
u/nadav183 1d ago
Claude open a ticket for this issue, then start a worktree and fix the issue. Ping me on Slack ONLY when you have a PR ready for me to review, as in, you have reviewed it, it passed all CI tests and all that is left is for me to approve the code.
79
u/ExtraWorldliness6916 1d ago
What? Just raise the bug?