Andrew Stopford's Weblog

Did you try to launch NCover from NAnt as a command shell instruction?

I did'nt use NAnt I tried this manually in the command shell. I am profiling a class lib so to do that I need to profile NUnit as it runs the unit tests on the lib. Interestingly it raises the error but clicking continue finishes the profile, however coverage data includes NUnit but not my lib.

I use the following commandline to execute ncover for my lib

"c:\Program Files\NCover\NC
over.Console.exe" /c "c:\Program Files\TestDriven.NET 1.0\MbUnit\MbUnit.Cons.exe" MyAssemblyToProfile.dll /a MyNamespaceToProfile /v

You have to run this command line in the debug directory since NCover requires the pdb files.

I use the following Nant script snippet to do code coverage in a automatic build

<property name="test.include.pattern" value="./Tests/**/bin/debug/*Tests.dll" />
<property name="ncover.executable" value="c:\Program Files\NCover\NCover.Console.exe" />
<property name="mbunit.executable" value="C:\Program Files\TestDriven.NET 1.0\MbUnit\mbunit.cons.exe" />

<target name="code-coverage">
<foreach property="assembly.name" item="File">
<in>
<items>
<include name="${test.include.pattern}" />
</items>
</in>
<do>
<property name="assembly.namespace" value="${string::replace(assembly::get-name(assembly.name), 'Tests', '')}" />
<exec program="${ncover.executable}" commandline="/c &quot;${mbunit.executable}&quot; ${assembly.name} /a ${assembly.namespace} /w ${path::get-directory-name(assembly.name)} /v" />
</do>
</foreach>
</target>

Hi,

You might find this of use:

http://blogs.conchango.com/howardvanrooijen/archive/2004/11/22/305.aspx