Angular code coverage testing is done via ng test --code-coverage. This uses istanbul under the hood by angular-cli to run code coverage checks. However, by default this will only cover source files that are covered by unit tests. This turns the code coverage check into a not very helpful metric, as we are only getting "What percentage of code paths weren't hit that could have been hit based on your existing unit tests" instead of "What percentage of your codebase isn't unit tested".
Angular code coverage testing is done via
ng test --code-coverage. This uses istanbul under the hood by angular-cli to run code coverage checks. However, by default this will only cover source files that are covered by unit tests. This turns the code coverage check into a not very helpful metric, as we are only getting "What percentage of code paths weren't hit that could have been hit based on your existing unit tests" instead of "What percentage of your codebase isn't unit tested".