Comments on: Writing Unit Tests for Pipeline Components with NCover http://www.modhul.com/2008/10/27/writing-unit-tests-for-pipeline-components-with-ncover/ Experiences of a UK BizTalk Consultant Wed, 01 Feb 2012 18:36:16 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Elton http://www.modhul.com/2008/10/27/writing-unit-tests-for-pipeline-components-with-ncover/comment-page-1/#comment-298 Elton Mon, 08 Dec 2008 12:24:59 +0000 http://www.modhul.com/?p=347#comment-298 Nice walkthrough Nick - worth noting that the discontinued versions of NCover are atill available here: http://www.ncover.com/download/discontinued. They're free and although there's no official support, they are stable and fully functional. The NCoverExplorer extras (http://www.kiwidude.com/dotnet/DownloadPage.html) are great for integrating NCover/NUnit into MSBuild and generating nice summary reports. Nice walkthrough Nick – worth noting that the discontinued versions of NCover are atill available here: http://www.ncover.com/download/discontinued. They’re free and although there’s no official support, they are stable and fully functional. The NCoverExplorer extras (http://www.kiwidude.com/dotnet/DownloadPage.html) are great for integrating NCover/NUnit into MSBuild and generating nice summary reports.

]]> By: Nick Heppleston http://www.modhul.com/2008/10/27/writing-unit-tests-for-pipeline-components-with-ncover/comment-page-1/#comment-271 Nick Heppleston Sun, 02 Nov 2008 13:22:57 +0000 http://www.modhul.com/?p=347#comment-271 Hi Joe, This method is now redundant from the codebase, but thanks for the feedback. Cheers, Nick. Hi Joe,
This method is now redundant from the codebase, but thanks for the feedback.

Cheers, Nick.

]]> By: Joe Feser http://www.modhul.com/2008/10/27/writing-unit-tests-for-pipeline-components-with-ncover/comment-page-1/#comment-269 Joe Feser Fri, 31 Oct 2008 14:00:12 +0000 http://www.modhul.com/?p=347#comment-269 The problem with the code is your file stream will never close if an exception is thrown. You should place that code in a using block, the steam will be closed and the exception block will still be visited (if it is an IOException). turn line 516 to 525 to use: using (filestream...) { //no need to flush or close, it will be done for you. } Joe The problem with the code is your file stream will never close if an exception is thrown.

You should place that code in a using block, the steam will be closed and the exception block will still be visited (if it is an IOException).

turn line 516 to 525 to use:
using (filestream…) {

//no need to flush or close, it will be done for you.
}

Joe

]]> By: Daniel Waldschmidt http://www.modhul.com/2008/10/27/writing-unit-tests-for-pipeline-components-with-ncover/comment-page-1/#comment-268 Daniel Waldschmidt Thu, 30 Oct 2008 18:53:26 +0000 http://www.modhul.com/?p=347#comment-268 Thanks, Nick! Just getting back from PDC2008 a few hours ago, we back at the office pounding away at the requests we heard from our users. Dan (Technology Apostle_ ----- We've been working hard to build the next generation of NCover. We're finally ready to show it off, and we feel confident that you'll love it as much as we do. We've reworked how we manage coverage data in NCover, and it has led to performance improvements in many operations, including loading coverage files. It has also finally united the way that NCover and NCoverExplorer work, giving a more fluid experience between the applications. With that unification process finally completed, we were able to drive forward with some new features that we're excited to tell you about. NCover 3 Beta includes Symbol and Branch Point Coverage, but it also has two new metrics - Cyclomatic Complexity and Method Visit Coverage. Cyclomatic Complexity describes the number of independent paths through your methods. It's a great indicator of when you should refactor, and code with a low cyclomatic complexity will help you guarantee that new developers on your teams can get up to speed fairly quickly. You can learn more about Cyclomatic Complexity at Wikipedia. While method visit coverage previously existed in NCoverExplorer, it only worked when you had symbol points for a method. With our new implementation you can guarantee that methods with no symbol points, including C# 3 automatic properties, have been tested. Our team has been dreaming of letting developers see how their coverage has progressed for quite some time, and in NCover 3 our dream comes true. Recording trends is as easy as using the append to trends (//at) flag in NCover. Once you've recorded trends you'll be able to generate html reports with graphs of how your coverage has changed over time and you'll also be able to see those trends in NCoverExplorer. We hated the way that NCoverExplorer in NCover 2 would close its tree view every time you reload coverage, so we fixed that. Now the tree view dynamically updates itself with your new coverage data and stays open just as it was before the reload. Also, the new NCoverExplorer tree view is able to display branch coverage and cyclomatic complexity in addition to symbol and method visit coverage that it supported in version 2. The statistics panel has been improved to show you more statistics. We now include various statistics on whatever item you have selected in the tree view, and if you have trend data loaded we show you a trends graph. Trends are available in the html report, too. We've got a great graph that works across all major browsers and lets you see just how well your coverage is improving. We felt like it was important to help you more strategically attack uncovered code, so we have replaced the old html report index with a new summary report that tells you the top 5 worst coverage offenders in several different categories. Since coverage is ultimately about digging in and writing tests for uncovered code blocks, we wanted to give you a way to find the blocks to attack at a glance. That's why we created the Uncovered Code Report. The Uncovered Code Report shows you your top 25 blocks of uncovered code so that you'll always have a good place to start improving your coverage. Thanks, Nick! Just getting back from PDC2008 a few hours ago, we back at the office pounding away at the requests we heard from our users.

Dan (Technology Apostle_

—–

We’ve been working hard to build the next generation of NCover. We’re finally ready to show it off, and we feel confident that you’ll love it as much as we do.

We’ve reworked how we manage coverage data in NCover, and it has led to performance improvements in many operations, including loading coverage files. It has also finally united the way that NCover and NCoverExplorer work, giving a more fluid experience between the applications. With that unification process finally completed, we were able to drive forward with some new features that we’re excited to tell you about.

NCover 3 Beta includes Symbol and Branch Point Coverage, but it also has two new metrics – Cyclomatic Complexity and Method Visit Coverage.

Cyclomatic Complexity describes the number of independent paths through your methods. It’s a great indicator of when you should refactor, and code with a low cyclomatic complexity will help you guarantee that new developers on your teams can get up to speed fairly quickly. You can learn more about Cyclomatic Complexity at Wikipedia.

While method visit coverage previously existed in NCoverExplorer, it only worked when you had symbol points for a method. With our new implementation you can guarantee that methods with no symbol points, including C# 3 automatic properties, have been tested.

Our team has been dreaming of letting developers see how their coverage has progressed for quite some time, and in NCover 3 our dream comes true. Recording trends is as easy as using the append to trends (//at) flag in NCover. Once you’ve recorded trends you’ll be able to generate html reports with graphs of how your coverage has changed over time and you’ll also be able to see those trends in NCoverExplorer.

We hated the way that NCoverExplorer in NCover 2 would close its tree view every time you reload coverage, so we fixed that. Now the tree view dynamically updates itself with your new coverage data and stays open just as it was before the reload. Also, the new NCoverExplorer tree view is able to display branch coverage and cyclomatic complexity in addition to symbol and method visit coverage that it supported in version 2.

The statistics panel has been improved to show you more statistics. We now include various statistics on whatever item you have selected in the tree view, and if you have trend data loaded we show you a trends graph.

Trends are available in the html report, too. We’ve got a great graph that works across all major browsers and lets you see just how well your coverage is improving.

We felt like it was important to help you more strategically attack uncovered code, so we have replaced the old html report index with a new summary report that tells you the top 5 worst coverage offenders in several different categories.

Since coverage is ultimately about digging in and writing tests for uncovered code blocks, we wanted to give you a way to find the blocks to attack at a glance. That’s why we created the Uncovered Code Report. The Uncovered Code Report shows you your top 25 blocks of uncovered code so that you’ll always have a good place to start improving your coverage.

]]>