StackOverflow has a rather extensive post which details many of the available code-coverage solutions for C#/.Net. Content reproduced below, and all credit should go to the users of SO:
Seems to be very popular and looks quite good
Supports statement coverage and branch coverage
$658 for a Desktop License
Older Beta-Versions available for free
Semantic Designs C and C++ test coverage tools can do this for MS source files. [There's a version that works with GCC, too.]
Along with running the instrumenter on the DLL source code, you'll need to add custom logic in the dll shutdown logic to dump test coverage data (or some other place that the dll executes rarely but reliably). The docs explain how ...
Depending on your platform you may go the route of using the link interface.
a) Your tests will import symbols. That's the used API.
b) Your software will export symbols. Substract a) to get unused API.
A tool simple as simple as nm would do the job then. Using the OpenSSL library on an ELF system as an example: this invocation gives you the imported ...
I've found out that it's possible to combine Travis CI and Codecov and run Coverage.py on Travis CI using this stucture:
This assumes that your are using the Python unittest module, other examples (for pytest and nose) can be found here:
Hope this ...
Semantic Designs' (my company) Test/Code Coverage Tools will collect code coverage data on an application regardless of whether it is exercised by a testing framework, by manual operation, simply during application execution, or during execution of the application as a server program if that is what it is.
They do so by instrumenting the source code; you ...
Our (Semantic Designs) Java Test Coverage Tool will do this. It isn't a library; rather it is a set of tools, but I think that is what OP meant anyway.
It operates by instrumenting the source code that you designate (on a class source file by class source file basis). This gives you a lot of control over what gets instrumented. It also means the test ...