dotCover vs Microsoft Code Coverage
dotCover
jetbrains.comMicrosoft Code Coverage
github.comSide by side
| Figure | dotCover | Microsoft Code Coverage |
|---|---|---|
| Price from | $50.75/mo | Free |
| Free plan | — | Yes |
| Free trial | Yes | — |
| Open source | — | — |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| Plans published | 2 | 1 |
| Spec score · Test Coverage Tools | 8.3 (#7) | 7.5 (#18) |
| Operating systems | On Windows, dotCover works as part of Visual Studio or Rider; on macOS and Linux, it is available only as part of Rider. | The supported operating systems include Windows, macOS, and multiple Linux distributions, with instrumentation support varying by OS, version, and architecture. |
| Purpose | dotCover is a .NET unit test runner and code coverage tool that reports statement-level coverage. | Measures what proportion of a project's code is exercised by coded tests such as unit tests. |
| Security | JetBrains says its tools adhere to industry security standards including SOC 2 attestation and makes SOC 2 reports, penetration testing report summaries, and security questionnaires available in its Trust Center. | The repository links to a security policy, but its README describes this repository as documentation and samples for closed-source coverage functionality. |
| Support | JetBrains provides technical support for product-related issues and directs users to its support resources. | The repository invites users to report issues related to the Microsoft.CodeCoverage and dotnet-coverage NuGet packages and Visual Studio code coverage functionality. |
| Test frameworks | The unit test runner supports MSTest, NUnit, and xUnit out of the box, and MSpec through a plugin. | With Microsoft.Testing.Platform.MSBuild, coverage extensions are auto-registered when installed with MSTest, NUnit, and xUnit runners. |
Plans
dotCover
- dotUltimate — individual$609 a year
- All Products Pack — individual$979 a year
In their own words
Microsoft Code Coverage
Microsoft Code Coverage measures how much of a project’s code is exercised by coded tests, such as unit tests. Its documented workflows cover.NET test projects with `dotnet test` and other.NET applications with the `dotnet-coverage` tool. It analyzes managed CLR and unmanaged native code using static or dynamic instrumentation; native coverage is disabled by default in the MTP extension. With Microsoft.Testing.Platform.MSBuild, extensions are auto-registered with MSTest, NUnit, and xUnit runners. The MTP extension can produce coverage, XML, and Cobertura reports, with settings for output, inclusion and exclusion rules, and instrumentation. It runs on Windows, macOS, and multiple Linux distributions, though instrumentation support varies by OS, version, and architecture. Other operating systems are supported on a best-effort basis, and some combinations allow static instrumentation only. Dynamic instrumentation on macOS and Linux requires libxml2, and missing dependencies may leave a report empty. MTP also excludes test assemblies by default unless configured otherwise. The plan is free.