Code Coverage

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…)

Today we are ready to introduce the first major release of ReSharper Ultimate family for this year – please welcome ReSharper Ultimate 2018.1! ReSharper gets a significant number of bug fixes (based on more than 260 requests) and a bunch of features and improvements as highlighted below: (more…)

Like all other products in the ReSharper Ultimate lineup, dotCover gets its set of improvements in the 2017.3 release. Let's check them out. Improved Show Covering Statements action Before 2017.3, after you used Show Covering Tests (Ctrl+Alt+K,T) in the editor, the popup window showed a list of covering tests. However, it didn't tell you what exact part of your code was covered by these tests:

Right after dotCover 2016.3 introduced a new way to highlight code coverage (markers in the gutter instead of colored backgrounds), we immediately got a flurry of “Bring it back!” comments. Indeed, there is a range of tasks where the “old-style” highlighting could be more useful, e.g. when you need to quickly evaluate uncovered parts of code. Some technological limitations prevented us from kee

After we released the initial continuous testing support in dotCover, the most popular response was "Cool, but this could be a lot more useful if highlighting was able to indicate test results." Indeed, before 2016.3, dotCover's highlighting was used only to indicate code coverage: dotCover 2016.3 finally addresses the issue. First, we got rid of colored backgrounds. Now, we use a small col

The recording of our June 10th webinar with Maarten Balliauw, .NET Code Coverage for Continuous Integration using TeamCity and dotCover, is now available on JetBrains YouTube Channel and slides on slideshare. In this webinar we use dotCover to collect code coverage information while running tests in our CI process. We can see how we can configure code coverage and how we can use the TeamCity Visu

Join us Tuesday, June 10th, 14:00 – 15:00 GMT (10:00 AM – 11:00 PM EDT) for our free live webinar, .NET Code Coverage for Continuous Integration using TeamCity and dotCover, with Maarten Balliauw. How much of our code is being covered by our unit tests? Are there areas we are not testing? By capturing code coverage data during a test run, we can analyze which areas of our applications are well-te

Using dotCover, we can run coverage analysis on our code. We can verify which portions of our project are covered by unit tests and which are not. However, there are times when we don’t want to perform analysis on our entire project and instead want to target certain areas. This can be because we want our coverage analysis to run faster or because we want to exclude third-party or obsolete assembl

JetBrains developers and QA engineers are finally going to have some sleep since dotCover 2.0 RTM is available right now for you to download. Here's the list of features that make this a worthy upgrade: Support for Visual Studio 2012 RC along with Visual Studio 2005, 2008, and 2010. As soon as Visual Studio 2012 RTM comes out, we're going to release a minor update to support it. Integrated un

In an earlier post, we saw how to use dotCover in simple scenarios, whereby we have a single unit test project for which we want to obtain coverage reports on. There are times however, when this is not the case; that is, we might have multiple tests projects. It is very common (and recommended practice) to separate Unit test projects from Integration test projects, allowing us to run the former mo