I have been working with some shitty organisation where they follow 100% code coverage. It sounds very good but it’s extremely frustrating to work on such test cases. If you are storing stack trace in DB to troubleshoot something. They expect to test stack trace also. Is it something wrong with me or it is really really really frustrating. Development is done in 2 days 7 days for testing 5 days in Pr review. Even tiny change takes whole Sprint. Anyone else in same boat TC- below poverty line
100% might be too strict, but you are just sounding lazy. Would you also be complaining at 85%?
I wish it was just write test case.
100% test coverage is bizarre. While I don't agree with it, if you abstract things into small functions it shouldn't be too difficult, but very tedious(like you mentioned). Does your company not have integration testing? From this post, it seems like they're trying to catch everything in unit tests which doesn't always work out even with 100% coverage
That’s funny part after 100% code coverage you deploy and your code doesn’t work because you forgot to add Serialization annotation
100% is ridiculous tbh 85% is doable and a good thing
100% of real written code should be also doable.. 85% is because you are probably not excluding autogenerated code from your coverage calculation.
Bingo. The numbers are meaningless. It's just an easy way for managers and tech leads to have the system enforce tests are being written instead of the painstaking process of reading very very carefully to see if the engineers did a good job. Realistically 100% or 85% or any number doesn't actually test the thing actually works. Your code could have a regex error and your coverage wouldn't catch it. It requires human decision making to find all the true edge cases.
Well they ask to write test case for all regex combination also
For simple regex 100 test case. Well that’s good but its pure mental harassment
Wow this sounds like a job for chatgpt tbh
Why don’t you put in a dict or something and loop over it?
Thanks for letting us know. We will avoid this org
What @Andy Jass means is that Amazon will avoid acquiring this company because it already meets or exceeds the Amazon pain threshold.
First of all 100% code coverage doesn't mean shit. It just means that every code path got executed, but doesn't mean anything with regards to accuracy. Also too many tests makes. Your code brittle and hard to change. Even a small change requires changing so many tests devs would be reluctant to do even small improvements.
Tech Industry
Yesterday
421
Does it make sense to move back to India for Indian techs in the US without a Greencard?
Personal Finance
Yesterday
1698
Thank you AAPL and NVDA
Personal Finance
Yesterday
585
Biden wants to raise capital gains tax to 40%
World Conflicts
Yesterday
639
Is "From the River to the Sea" So Wrong?
Tech Industry
2d
7915
What happens when most of your team is Indian?
Just write tests. Don't be lazy
100% is way too much. I know exactly what OP means. At that level, you’re testing the most inane interactions.
^ I second this. It is not worth it for general engineering. Every next % above 88% increases in cost, probably yet another example of the paretto principle. 95% is good enough in most cases, unless we are talking about health care, or sensitive components that could cause human life threats, fatalities, or damage. OP, give more details so we can jerk on it 🫠 Also, could you combine multiple reports/coverage?