ProgrammerHumor
onlyFewHundredErrors
Discussion
Why write tests if they will be ignored?
Great point, I should stop writing tests.
Yes. I mean - you wrote the code, why write even more code that will check “yes the code you wrote is still there”. Lol, lmao even.
Not sure if sarcasm or not tbh
Classic misuse of this meme where the right side is still intermediate
This sub is the champion of misusing the meme
Plenty of people that are in the left side believe they are in the right side.
It's even worse.
Being on the left side makes it actually more likely to believe to be on the right side.
[deleted]
This comment is just the best kind of bait.
We don't read documentation on memes.
That's not how the meme works
Reminds me of this friend's startup that was built to be scalable to 10's of millions of users and hundreds of developers for months and months and months. They have about 100 users and running out of $.
Coverage says basically nothing about how well tested the software is
OK but deploying with failed tests tells me a lot
Definitely
Don't show my PM, he'll get cursor to add it
Alright, whose project manager wrote this?
considering how normal it is to test your code and how pretty much every developer hates it - it’s weird there isn’t a bigger demand for software testers with an engineering background to help creating more valuable unit test suites so we don’t have to give a shit about coverage anymore.
That’d mean spending money on something that PM’s rarely want to spend time on
after fighting all day with tests I can proudly say we have gone from 56% to 57% test coverage. We are no longer in the last group
noob here, what the heck are tests?
list of inputs and expected outputs to make sure your code is working correctly
That's what I use basic output for :D
So the genius has 1.2k users using his broken app? He may be a genius at something, but I'm not sure it's software engineering.
Windows be like:
The badges help you get users. The users help you realize the badges mean nothing.
Coverage 100 or even 95 is a lie at least in my personal experience, instead of do actual feature testing they just do whatever to cover a line of code that may be should nt be there in the first place to get high coverage
You have the right to put yourself on the right but, just so you know, it's not how you're supposed to do it
No, the tests would be passing on the right.
But coverage would be for the important parts, and would actually test shit, and not just run code lines.
No experienced developer has tests that doesn't pass, since everything is automated based on the tests passing. But a senior also knows when prioritize testing, instead of just chasing a metric for the percentage of lines ran.
Often times I'll see formatting or linting checks combined in with tests, and those often fail even when tests pass. I usually see it when a project uses standard library items that are later deprecated.
If lint fails you don't let it merge, and it can be fixed with one click.
Those would usually be done on PRs by themselves and not as regular tests, but sure, PRs would require them to pass as well.
They'll usually be part of a pre-commit hook to format the code to the project's standard.
I've also seen huge projects with tests flakier than grandma's pastry
I love when the whole testing suite fails because one method from a 3rd party library or api call doesn't follow camel case. I have to go ask my principle dev before I can add an exception to the lint rule... fun.
I took this meme to be in the context of FOSS projects. 1.2k users is like the sweet spot for those projects where it's just one dude maintaining it in his limited free time and can't be assed to keep all the tests and linting up to date but the project is still 100x better than the proprietary alternative.
Broken window syndrome. If some of your tests always fail, the rest that work are not really useful
EDIT: I mean to say I agree with you. Better to have fewer, relevant tests that pass and check important stuff that many low quality tests with some always failing. Even if you have the good tests, if you add bad tests, the good tests lose value
cries in management mandated code coverage numbers
Yep, I removed a shit ton of tests in a project previously, cause it was testing that the mocked value returned the mocked value... And I was like, these tests are junk.
Yeah what crack is the person smoking putting on the right? It’s not hard to get high coverage though. It’s hard to get it set up for high coverage but that’s about it