Real coverage test would test coverage OF THE SPECIFICATION. So for a list of statements describing how your service should behave in various situation you would want to know which are being verified by the unit test.
Checking lines of code is pointless because line of code would usually be required for multiple specification statements (requirements).
There is barely any connection between having 100% line coverage and covering entire component specification.
I think unit coverage are those measures where somebody thought they need to measure something but they could either not define what to measure or they deciding that measuring the right thing is too difficult so we can measure something else instead and managers will be happy anyway.
Real coverage test would test coverage OF THE SPECIFICATION. So for a list of statements describing how your service should behave in various situation you would want to know which are being verified by the unit test.
Checking lines of code is pointless because line of code would usually be required for multiple specification statements (requirements).
There is barely any connection between having 100% line coverage and covering entire component specification.
I think unit coverage are those measures where somebody thought they need to measure something but they could either not define what to measure or they deciding that measuring the right thing is too difficult so we can measure something else instead and managers will be happy anyway.