On 4/12/20 6:55 AM, Kevin Malachowski wrote:
[External Email. Be cautious of content]
Is there a particular reason you want 100% code coverage?
In this case, I'm writing code that will be the introduction of go to a
team of which I am now a fresh member. 100% code coverage opens eyes.
And the fact that it is even plausible for go packages is, I suspect, a
selling point to management.
But I agree that it can easily be a time sink. I haven't done it before
so I'm still trying to overdo it before settle into what I will
eventually decide is reasonable.
Thanks.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/66526d9a-2cb5-5896-a618-72bb658abfc1%40juniper.net.
