Code coverage tools are generally specifically about test coverage, not which code actually gets executed or is unreachable. It makes sense in swift because code with tests would still report as being covered even if the actual UI that would ever run that code was removed. That’s what this tool looks for. Dead code, not untested code
Code coverage tools are generally specifically about test coverage, not which code actually gets executed or is unreachable.
Code coverage tools are for whatever you want to use them for. Lots of people use them to measure test coverage, but you can also use them to measure code usage in production. There are a variety of different ways to instrument code of various different levels of invasiveness and performance impact. Even the Linux kernel has built in instrumentation for measuring code coverage (kcov).
Was it really useful? Code coverage tools have existed for forever. Does Swift not have any FLOSS coverage tools like
gcov?Code coverage tools are generally specifically about test coverage, not which code actually gets executed or is unreachable. It makes sense in swift because code with tests would still report as being covered even if the actual UI that would ever run that code was removed. That’s what this tool looks for. Dead code, not untested code
I know what the tool does, I read the webpage.
Code coverage tools are for whatever you want to use them for. Lots of people use them to measure test coverage, but you can also use them to measure code usage in production. There are a variety of different ways to instrument code of various different levels of invasiveness and performance impact. Even the Linux kernel has built in instrumentation for measuring code coverage (kcov).