You're describing e2e tests. They're easier to write but it's harder to test all the paths and the tests take more time. I prefer to use both e2e tests for main paths and unit tests with mocks to ensure there's high code coverage.
Code Coverage has no value. It's the most garbage metric on the planet. I can write you a test suite that achieves 100% coverage and doesn't test a single thing. Stop using that metric, it doesn't mean anything, anything at all.
@@LeutnantJoker I disagree. There is a code coverage metric named "beaches". It's one of the most valuable metric when it comes to testing. Keeping that metric at high percentage ensures every condition is tested. Having 100% lines coverage may not be a reasonable goal, but having high percentage of branch coverage definitely is.
If only my teammates could understand. I'm trying to explain the same to them and it looks like talking to a wall. I even had 1 person saying (btw. he has 7y of exp) "unit tests are more important than integration tests". Dude, if your graphics card, cpu, ram work separately - it doesn't mean they will work properly joined together. Then another person keeps creating mocks in integration tests or keeps verifying that serviceA was called x times in a unit test. I tried to explain to them multiple times that changing the implementation shouldn't break a unit test because we can't fix/improve the code and we should be able to verify that it still behaves the same. The answer always was "yeah, then in this case you should fix the code" and the entire team is like "yeah, I agree". Man, I'm already sending my resume and can't wait to change my job... I'm just tired of that shit... I feel like I'm working with interns but these people are almost 10 years in the business...
![ILLSLICK - KILLSHOT REMIX [FULL VERSION]](http://i.ytimg.com/vi/RIK8RrqIAzE/mqdefault.jpg)
You're describing e2e tests. They're easier to write but it's harder to test all the paths and the tests take more time. I prefer to use both e2e tests for main paths and unit tests with mocks to ensure there's high code coverage.
Code Coverage has no value. It's the most garbage metric on the planet. I can write you a test suite that achieves 100% coverage and doesn't test a single thing. Stop using that metric, it doesn't mean anything, anything at all.
@@LeutnantJoker I disagree. There is a code coverage metric named "beaches". It's one of the most valuable metric when it comes to testing. Keeping that metric at high percentage ensures every condition is tested. Having 100% lines coverage may not be a reasonable goal, but having high percentage of branch coverage definitely is.
@@j3bb9z I can achieved 100% branch coverage without testing a single thing. The metric is BS
@@LeutnantJoker You don't know what you're talking about. But I'm not going to waste my time convincing you. Do as you wish.
I learned a lot! Thanks for the video :)
hey that's awesome! I'm so glad you that you were able to find it useful!.
In big apps unit tests are also a way to track changes, if youve changes something important test should highlight it
agreed the best tool to protect against regression
If only my teammates could understand. I'm trying to explain the same to them and it looks like talking to a wall. I even had 1 person saying (btw. he has 7y of exp) "unit tests are more important than integration tests". Dude, if your graphics card, cpu, ram work separately - it doesn't mean they will work properly joined together. Then another person keeps creating mocks in integration tests or keeps verifying that serviceA was called x times in a unit test. I tried to explain to them multiple times that changing the implementation shouldn't break a unit test because we can't fix/improve the code and we should be able to verify that it still behaves the same. The answer always was "yeah, then in this case you should fix the code" and the entire team is like "yeah, I agree". Man, I'm already sending my resume and can't wait to change my job... I'm just tired of that shit... I feel like I'm working with interns but these people are almost 10 years in the business...
Yep, integration tests are much more important.