Tell that to SQLite guy.
Tell that to SQLite guy.
SELECT code execution from using SQlite - DEF CON 27 Conference
https://www.youtube.com/watch?v=HRbwkpnV1Rw
Don't get me wrong, it's a great product and I use it often, but 100% test coverage does NOT equal 100% safe.
Try that with a networked application that takes user input though...
It will always break on the user's internet, because it's too diverse to predict.
Doesn't mean you can't have some networking unit tests, just that you shouldn't believe in them too much.
Edit: you said services. You thinking of server? I'm thinking of clients.
And it doesn't have to be a static mock. It's not too hard to inject a fuzzer in your mock service response, although that's probably left to a separate testing routine, and not part of your unit test setup. But if you have no mock for your network service, you can't fuzz it either.
Which shows 100% unit test coverage is not better than spending that time in other kinds of tests.
SQLite is suitable for 100% coverage.
A lot of application code or workflow style code is hard to reach 100% coverage as they are rarely triggered.
That's an opportunity to describe, in code, what that path is supposed to do, and then make sure it does it.