Probably a bug in the NCover merge tool.  You have two alternatives.

1. Run each test project independently.
2. NCover.Console ...args...... Gallio.Echo ...args... /r IsolatedAppDomain

Jeff.

On Tue, May 11, 2010 at 1:38 PM, Mauricio Scheffer <
[email protected]> wrote:

> Hi,
>
> I just upgraded a project to a nightly build of Gallio 3.2 and noticed
> that the coverage report of multiple test projects gets merged using
> NCoverExplorer. Is there any way to turn off this merge? I'm using
> Gallio through the msbuild task, NCover 1.5.8, NCoverExplorer 1.4.0.7
>
> The reason I'm asking this is because it seems to have some issues...
> or maybe it's something I don't understand:
> I have a class under test with a single method Validate() that returns
> IEnumerable<Something> and this method is implemented with yield
> return.
> In the merged coverage report it says:
>
> MyClass
> - <Validate>d__0 (37%) (which is the private enumerator class
> generated by the compiler)
> - - MoveNext (0%)
> - - MoveNext (100%)
>
> So there's a duplicate MoveNext, one of them with 0% coverage (?) and
> the total coverage is 37% even though I *do* have 100% coverage of
> this method (as shown in the second MoveNext line)
>
> Has anyone seen this? Any ideas?
>
> Thanks
> Mauricio
>
> --
> You received this message because you are subscribed to the Google Groups
> "MbUnit.User" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<mbunituser%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/mbunituser?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"MbUnit.User" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/mbunituser?hl=en.

Reply via email to