A code coverage tool for .NET 2+ on Windows, supporting 32/64-bit processes with branch and sequence point coverage.
OpenCover is a code coverage tool for .NET applications running on Windows, designed to measure how much of your code is executed during tests. It supports both 32-bit and 64-bit processes and provides detailed coverage data including branch and sequence points. The tool helps developers identify untested code paths and improve test suite effectiveness.
.NET developers and teams working on Windows-based applications who need to assess test coverage for unit and integration tests. It is particularly useful for those using CI/CD pipelines and requiring coverage reports for quality assurance.
OpenCover offers a robust, Windows-native solution for .NET code coverage with support for complex scenarios like IIS and Windows Services. Its ability to handle 64-bit processes and provide both branch and sequence point coverage sets it apart from earlier tools like PartCover.
A code coverage tool for .NET 2 and above (WINDOWS OS only), support for 32 and 64 processes with both branch and sequence points
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports both 32-bit and 64-bit processes for .NET Framework 2 and above on Windows, addressing a gap left by older tools like PartCover.
Tracks branch coverage for decision paths and sequence points for individual instructions, providing fine-grained insights into test execution.
Includes documented guidance for covering complex scenarios like IIS, Windows Services, and Silverlight, making it practical for integration testing.
Works with CI systems like AppVeyor and includes NAnt scripts for automated building and testing, facilitating seamless integration into development workflows.
The project is in archive mode, with development sporadic and only occasional security patches via Dependabot, limiting future support and updates.
Does not support Mono and has issues with .NET Core; using the `-oldstyle` switch is a workaround, but compatibility is not guaranteed for modern .NET versions.
Building from source requires specific tools like Visual Studio 2019, WiX, and multiple .NET SDKs, making it cumbersome for customization or contribution.