What's under the hood? |
1.5.8 β |
2.1 Pro. |
2.1 Ent. |
| Comprehensive Code Coverage Analysis |
| | |
| NCoverExplorer Included |
 |
 |
|
|
NCoverExplorer, the most popular tool for analysis of NCover profiling data
is now included in the NCover package. NCoverExplorer is a tool that allows you to
browse your coverage data at the source level, highlighting the code that needs more
testing. NCoverExplorer can generate a set of summary reports in HTML for sharing
your coverage analysis with the rest of the team.
|
| Comprehensive Language Support |
|
|
|
|
Because NCover does its analysis at the .NET runtime layer, it does
not matter which .NET language you choose to use for your project. NCover
will work with any language that compiles to managed code. We've tested
NCover with C#, VB.NET, Managed C++, J#, MSIL, and Boo.
|
| No Special Builds Required |
|
|
|
|
Other code coverage tools require you to build a specially modified build of your
software for analysis. NCover enables you get more accurate results by running its
analysis on the same code that ships to your customer.
|
| Sequence Point Coverage Reporting |
|
|
|
|
Sequence point coverage tells you which sequence points have been
executed in a particular test run and how many times the code at each sequence point
has been executed. "Sequence points" are defined by the compiler and they represent
each point in the program where the debugger can pause execution. For the most part,
there is a sequence point for each executable line in a source file, but on occasion
there can be multiple sequence points in a single line.
|
| Branch Coverage Reporting |
|
|
|
|
Branch point coverage extracts the execution flow graph from each method and reports
how many times the code in each branch segment was executed. There are fewer branch
points than sequence points in a program and each branch represents one and only one
branching path through your code.
|
| Easy To Use |
| | |
| XML Coverage Data Output |
|
|
|
|
NCover can save the coverage data into a simple and easy-to-read XML output
file. The XML coverage file can easily be processed for analysis or integrated
into a continuous build environment.
|
| Detailed HTML Coverage Report (Examples) |
|
|
|
|
NCover will now produce a comprehensive html report on your codebase, showing coverage
statistics and source code by module, namespace, class, method and source file. Data in
the report can be sorted on the fly to highlight which sections of code need more tests.
|
| Settings File/Project Support |
|
|
|
|
When building a complex profiler configuration, it can be helpful to save the settings
in a file, rather than building a complex command line. Instead of building the full
command-line simply specify the settings file and NCover will read its settings from the file.
|
| NAnt/MSBuild/CC.Net Integration |
|
|
|
|
NCover is most useful as part of an integrated, automated, continuous build environment.
In order to facilitate your automated build process, NCover includes add-ins for NAnt,
MSBuild and Cruise Control.NET that allow these tools to work together effectively.
|
| Precision Targeting |
| | |
| Select Assemblies to Profile |
|
|
|
|
Choose which assemblies you want to include in coverage profiling. By selecting
assemblies to profile, you can eliminate the clutter of infrastructure and test code
and focus your coverage analysis on the code that is under test in a particular test
fixture.
|
| Attribute-Based Exclusion |
|
|
|
|
Exclude code from coverage based on .NET attributes. Methods or classes can be
excluded from coverage by putting attribute metadata on the respective class or method
and then informing NCover of the attribute name. You do not have to reference any
NCover assemblies. Any attribute will do.
|
| Auto Exclusion of Compiler-Generated Code |
|
|
|
|
The compiler can generate sequence points that are convenient for debugging, but do not
relate to lines of code written by the developer. Examples of this include compiler-generated
code and No-Ops inserted for the debugger.
|
| Type Exclusion (RegEx Pattern) |
|
|
|
|
You can instruct NCover to exclude a set of types (classes) from coverage by specifying
a list of regex (regular expression) patterns that match the full type name.
|
| Method Exclusion (RegEx Pattern) |
|
|
|
|
You can instruct NCover to exclude a set of methods from coverage by specifying
a list of regex (regular expression) patterns that match the method name.
|
| Source File Exclusion (RegEx Pattern) |
|
|
|
|
You can instruct NCover to exclude the types and classes from a set of
source files by specifying a list of regex (regular expression) patterns that
match the source file names.
|
| Professional Strength |
| | |
| Symbol Search Policy |
|
|
|
|
NCover searches for symbol files in order to get the mapping between your source code
and the compiled .NET assembly. The symbol search policy tells NCover whether to search
any of the following places for symbol information; the Windows registry, a symbol server,
the original path, the reference path.
|
| Child Process Profiling |
|
|
|
|
Profiling a process that is launched by another .NET process can be tricky. NCover
helps with this by allowing you to specify the name of the process you want to be profiled.
NCover will wait until the specified process is launched before attaching the profiler.
|
| IIS (ASP.NET) and Windows Service Profiling |
|
|
|
|
NCover provides support for analyzing ASP.NET code running in IIS
as well as .NET code running in Windows service applications with the //svc option.
Setting up a profiler to capture data from IIS or another Windows service is fiendishly
difficult. NCover has now automated this process. By setting a few simple command-line
options, you can easily gather code coverage data from your service application.
|
| Expertly Supported |
| | |
| Detailed Documentation |
|
|
|
|
NCover now comes with detailed documentation. In previous versions, as a community
supported tool, NCover had insufficient documentation. With NCover 2.0, there is a
wealth of information in the documentation section, making your job easier as a developer.
|
| Community Forum Support |
|
|
|
|
NCover has an open community of users which help each other use
NCover to its full potential. You can participate in the forums by
going to the support section of the NCover web site.
|
| Expert Email Support |
|
|
|
|
NCover is now a fully supported product. When you purchase a license, you will receive
comprehensive email support from the dedicated NCover development team. No longer will
you have to wait to have your questions answered.
|
| Software Update Subscription Available |
|
|
|
|
With the NCover software subscription plan, you will have all NCover software updates
sent to you for the lifetime of your subscription. We plan to deliver at least one major
release each year with minor updates and bug fixes in between.
|
| Windows XP/2003/Vista Support |
|
|
|
|
NCover 2.0 Professional is fully tested and supported on Windows XP SP2, Windows Server 2003 R2
and Windows Vista.
|
| Windows XP x64/2003 x64/Vista x64 Support |
|
|
|
|
NCover 2.0 Enterprise is fully tested and supported on the 64-bit .NET runtime.
Supported 64-bit operating systems include Windows XP SP2, Windows Server 2003 R2
and Windows Vista.
|