SourceForge confusion

There is an old 1.0 something build on sourceforge which I have been using for a little while. Why don't you put a link from there to here or mirror your releases on their site? You might get more people using it that way...

Re: SourceForge confusion

There is no link because it is not the same product - it is someone else's long dead attempt at a code coverage product also called NCover.

Re: NCover with MSTest

Has anyone else been able to get NCover working with MSTest ??

Please post a reply if you have!

Re: NCover with MSTest

There is an undocumented commandline switch that will allow NCover to gather coverage info: noisolation.

Re: NCover with MSTest

I cannot get NCover to produce any coverage information when using MSTest. This is done from a command line batch file...

MSTest command is of the form:

SET testFile= "/TestContainer:F:\MyProject\bin\Debug\MyTest.dll"
SET MSTest= "C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\mstest.exe"
SET MSTestCommand= %MSTest% /nologo /noisolation %testFile%

My NCover command is:

SET NCoverExe= "C:\Program Files\NCover\NCover.Console.exe"
SET Assemblies= My.dll
SET WorkingDir= "F:\MyProject\bin\Debug"
SET CoverageOutput= //x "F:\MyProject\CoverageOutput.xml"

%NCoverExe% %MSTestCommand% //a %Assemblies% //w %WorkingDir% %CoverageOutput%

All I get in my CoverageOutput.xml is the following:

<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="coverage.xsl" type="text/xsl"?>

<coverage />

The Command line output indicates that the MSTest tests have been executed and have all passed so soemthing is happening - just that NCover isn't picking up MSTest running.

Nigel