Unit test coverage and continuous testing. Now in Rider!


With each Rider release, we do our best to bridge the gap between Rider and the ReSharper Ultimate bundle. The top in-demand feature has certainly been “Rider + dotCover” integration. So, without further ado, please welcome the latest Rider 2018.2 EAP build – the first Rider version ever that features unit test code coverage and support for continuous testing!

What exactly is dotCover able to do in Rider, and how is it going to be licensed? Read the answers below.

What operating systems are supported?

Currently, only Windows is supported. Support for Mono is still a work in progress and not going to be included in 2018.2.

How is it installed?

dotCover is provided as a bundled plugin for Rider, and installed along with Rider automatically. No additional actions needed! If for some reason you want to disable dotCover, you can do this via Rider’s Plugins settings:

dotCover in Rider. Plugin settings

How will it be licensed?

We don’t want to reinvent the wheel and confuse anyone with additional licenses. Since dotCover is normally part of ReSharper Ultimate, all coverage functionality in Rider will be available only for the ReSharper Ultimate + Rider bundle (and of course for the All Products Pack).

What features are already available?

All critical functionality is already here and available starting with the latest EAP. First, it’s “classic” unit test code coverage analysis using Coverage Tree and code highlighting. Everything looks and feels exactly the same as in Visual Studio with ReSharper Ultimate:
dotCover in Rider. Unit tests code coverage

Continuous testing is also here and has no differences compared to ReSharper Ultimate. Simply enable it for the desired session, change the code and build or save the project (depending on the preferences).

dotCover in Rider. Continuous testing

Note that the continuous testing trigger (build or save) can be set in Unit Testing settings:

dotCover in Rider. Continuous testing settings

If you’re new to the continuous testing feature, find more details in this post.

What features are NOT yet available?

The following dotCover functionality is not present in 2018.2 (but will definitely be in the scope of future releases):

  • Code coverage of applications
  • Coverage filters
  • Coverage reports (XML, HTML, etc.)
  • Document summary
  • Hot Spots view
  • Continuous testing indicator
  • Opening coverage snapshots
  • Search in Coverage Tree

It’s still possible that some of these will make it into the 2018.2 release, but not likely.

You’re welcome to download the latest Rider 2018.2 EAP and check its coverage capabilities by yourself. And of course, we would be glad to hear your opinion in the comments below!

This entry was posted in How-To's and tagged , , , , . Bookmark the permalink.

23 Responses to Unit test coverage and continuous testing. Now in Rider!

  1. Vadim Yarovikov says:

    Waited for this for a long time, thanks!

  2. Nathan says:

    this is great, but if i’m in windows i’m using visual studio. we need this and a host of other features to be available in all platforms before people can realistically look at using Rider full time.

  3. dstanleywrberkley says:

    This may be a stupid question. You mentioned it would be part of the Resharper Ultimate and Rider bundle. What if they are split under different licenses? I assume it would work, but thought I would ask. My company has bought us Resharper Ultimate licenses and I purchased an Individual license for Rider, both registered under the same Jetbrains account.

    • Alexey Totin says:

      it is a separate ‘ReSharper Ultimate + Rider’ license that is required by the feature to run. So, unfortunately, it won’t work in your case. Nevertheless, if the licenses you have are both ‘personal’, we could send a request to our sales to upgrade them into a single R+R license.

  4. Got really excited about this then spotted that it was for Windows only. Any rough ETA on Mac compatibility?

    • Carl Thomas says:

      I too was looking around for this for a while until I saw this comment. This is the only feature I am missing in Rider now. As said before please state an ETA for this feature.

    • Alexey Totin says:

      Hi Joseph,
      first of all, thanks a lot for your interest in Rider. This is by any means not a strict ETA, but we do hope to add support for Mono on Unix systems in 2018.3.

  5. A Mac User says:

    Presumably there’s a discount for Mac & Linux users considering they get less functionality? Disappointing that you are willing to break feature parity across platforms.

    • Daria Dovzhikova says:


      We are not going to break feature parity across platforms but making dotCover available for Mac and Linux users takes longer than for Windows.

  6. Pingback: The Morning Brew - Chris Alcock » The Morning Brew #2627

  7. Pingback: Dew Drop - July 23, 2018 (#2771) - Morning Dew

  8. Poor at english says:

    I have not ReSharper + Rider but all products pack lisence.
    Can I utilize this feature?

    • Alexey Totin says:

      Yes, absolutely. The ‘All products pack’ license is some kind of superset that includes R+R and other IDE licenses.

  9. Richard Collette says:

    It’s curious that Windows was made the leader for the coverage feature. Given that the majority of Windows .NET developers are probably using Visual Studio anyway, I would have thought that bringing the feature to Mac first would have made more sense.

    • Alexey Totin says:

      Hi Richard,
      this is not because we anyhow prefer Windows over other platforms.
      All our dotNet tools (dotCover, dotTrace, and dotMemory) use a common profiling core that was initially developed only for Windows. So, there was no choice “Mac or Linux or Windows”. We’ve implemented what we already had. Talking about the support for Mono on Mac and Linux: it is really a huge work that takes some time.

  10. Yaroslav says:

    Why not to use AxoCover?

  11. Nathan Boyd says:

    Since non-windows systems are not supported, I tried Scott’s approach with VSCode, he integrated coverlet and some VSCode Extensions to provide coverage along with gutter markup. its working great.


  12. Hugh says:

    If I only use Rider (on Linux), what would be the purpose of me getting a Resharper license at all? Getting Resharper Ultimate seems redundant (and a waste of money) if I don’t use Visual Studio.

    • Alexey Totin says:

      Hi Hugh,
      currently, coverage is available only for Windows. When it comes to Linux, it is possible that we will revise the licenses.

      • Hugh says:

        Thanks Alexey

        I’m more interested in continuous testing, but coverage would also be useful.

        Wouldn’t the plugin mechanism enable customers to “build up” a customised version of Rider with the features they want/need?

        • Alexey Totin says:

          In our case, continuous testing can’t exist without coverage, so, one always goes with the other. About plugins – yes, but in the same way as in IDEA: support for other languages and frameworks, dotCover, dotTrace, and so on. But the initial ReSharper functionality Rider is based on is not supposed to be somehow divided into plugins.

      • Dylan says:

        Any update on this? I’m using Rider on Mac, so don’t need ReSharper – but want to use dotCover. I can’t convince my company to upgrade us all to ReSharper ultimate, but I think if dotCover was available standalone, I’d probably be able to convince them to get it.

        • Alexey Totin says:

          Hi Dylan,
          at the current moment, the licensing model stays as it is. So, to get dotCover in Rider, you should upgrade to RSU+RD license. The cost of the upgrade is not that big compared to the cost of the license. Personally, I think, the problem is in the license name – RSU+RD and not in the price. People tend to think they buy “ReSharper + some stuff” but in fact its a set of equally valuable products.

Leave a Reply to Alexey Totin Cancel reply

Your email address will not be published. Required fields are marked *