unit test coverage
dotCover, dotMemory, dotPeek, and dotTrace 2021.3 Release!
dotCover 2021.3, dotMemory 2021.3, dotPeek 2021.3, and dotTrace 2021.3 have been released and are ready for downloading! Before diving into the feature set, we need to make an important announcement. Starting with the 2021.3 release, we have discontinued support for the x86 versions of dotMemory Standalone and dotMemory Portable. You can still use dotMemory x86 from the previous releases. Now, let’s take a quick look at the 2021.3 release updates in these tools. dotCover 2021.3 The dotCover command-line runner now works on computers with Apple silicon processors. It can p
Rider 2020.3: .NET 5, C# 9, F# 5, Immediate Window, Project Dependency Diagram, and Updates to Unity Support
Hello everyone! For the last 4 months the whole .NET division here at JetBrains has been working hard on preparing some awesome stuff for you in the last Rider release of this year. We hope you will enjoy all the new features and improvements. Say hello to the Rider 2020.3 release! Here are the most notable new features in this release. .NET 5 Rider supports all of the features from the latest versions of .NET including source generators, new NuGet features, and new target frameworks (net5.0-windows and net5.0). C# 9 All the new features from C# 9 are finally supported in Rider: reco
Rider 2020.1 Is Released!
Hello everyone, We’ve published Rider 2020.1 today! Let’s talk about the most important updates we have for you in this release. The backend runs on .NET Core runtime Finally, the backend runs on .NET Core runtime by default on macOS and Linux, instead of the Mono runtime. Moving to .NET Core runtime delivers noticeable performance improvements, a lower memory footprint, and multithreaded NuGet restore. (more…)
Rider 2019.3 Release Is Out!
Hello everyone, We published Rider 2019.3 just moments ago. Let’s walk through the key improvements in this update which the Rider team has focused on for the last four months. Let’s highlight the most important features in this release: (more…)
Cross-Platform dotCover Console Runner and more – What’s New in dotCover 2019.2
In the 2019.2 release, the dotCover team was mainly focused on the console runner tool. The result is some good news about the tool, including one important fix specially for .NET Core users: The dotCover console runner is available not only on Windows, but on macOS and Linux as well. The console runner can perform coverage analysis in Mono projects and gets a new command for analyzing .NET Core projects. The issue with 0% coverage and .NET Core unit tests was fixed. The dotnet dotCover test workaround is no longer needed, but you can still use it if you find this way of running covera
Rider 2019.2 is released!
Hello everyone, We have good news for you today – Rider 2019.2 is released and ready for you to download! Here are the biggest and best things about Rider 2019.2: (more…)
Rider 2019.1 Has Arrived!
Today we are thrilled to introduce this year’s first major update for Rider – please welcome Rider 2019.1! With this release, Rider 2019.1 gets a new pack of features and improvements: (more…)
ReSharper Ultimate 2018.3.1 bug-fix update is here
Today, we invite you to download the first bug-fix build for ReSharper Ultimate 2018.3 release – ReSharper Ultimate 2018.3.1. This bug-fix update resolves the following issues: (more…)
Rider 2018.2 is released
We are excited to introduce to you the new Rider release - please welcome Rider 2018.2! This release comes with a solid set of bug-fixes, and a bunch of new features and improvements which are highlighted in the list below: Debugger: call stacks are now displayed in a more understandable way, thread-specific breakpoints have been introduced, and inspecting and expanding unsafe pointers is now supported. Docker support has reached the debugger: It is now possible to debug ASP.NET Core apps in a local (Linux) Docker container: inspecting variables, the stack frames, threads, as well
Rider 2018.2 Release Candidate
If you can’t wait to get your hands on Rider 2018.2, great news: please welcome the Rider 2018.2 Release Candidate! A lot of you have been contributing to our EAP and so are fully aware of the changes coming in the 2018.2 release. This is a good time to say ‘Thank you!’ to all you EAPers for sharing your feedback on the latest features and improvements we’ve introduced. It’s been extremely valuable! Let me quickly highlight the most notable changes to look forward to in 2018.2: Debugger: more understandable call stacks, thread-specific breakpoints, and you can now inspect and expand
> dotnet dotсover test
Important: This post is outdated. Please use the instructions from the dotCover documentation. If you've got the idea of this post just by reading the title, you may skip the next paragraph and go right to the procedure. We're going to talk about the dotCover.exe console runner and a new way to run coverage analysis of unit tests. While the dotnet tool simplified running tests a long time ago (dotnet test in the working directory is enough), dotCover.exe still required you to specify a lot of arguments in order to run tests, like an absolute path to the dotnet.exe, path to a .dll with te
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. (more…)