Re:Write tests. Not too many. Mostly integration (2017)
by kristiandupont on Friday February 01, 2019 @05:16AM
(#19053018)
>I still think my testing procedures were better than nothing.
I am sure they were, but you also said:
>take the time to understand why they want 100% coverage
which to me indicates that they are under the false impression that this gives some sort of completeness, i.e. "make sure this plastic fence covers the entire stretch of mountain road".
We have a coverage threshold of 90% and it is helpful because it works as a reminder if you try to check in code that isn't covered by tests. I think that pushing that to 100% would add little value but a lot of overhead. Never tried it though so I fully admit that it's just my hunch.
Re:Write tests. Not too many. Mostly integration (2017)
by kwhitefoot on Friday February 01, 2019 @03:59AM
(#19052676)
I feel for you. I argued for unit testing for ten years before they were instituted and even then it was half hearted.
The senior engineers were not supportive of other forms of testing in any way (even the user testing). They flat out refused my proposal to attempt to create an integration test suite to cover it's communication to other services as well as other services consuming it's data (this I started over the weekend and was told to proceed no longer).
tl;dr: You're absolutely correct but I still think my testing procedures were better than nothing.