CharliePoole

If this is confirmed, it's probably also a V3 issue.

We should check for an nunit bug then. Nunit should be providing the proper class name. On Dec 17, 2013 5:15 AM, "mnivet" [email protected] wrote: > I've got some tests...

We haven't used Launchpad for a long time. Can you point me to the discussion in question? Right now, this is not a problem that's on our radar, but if...

Sorry, I see the discussion is cited above. @OsirisTerje This has never been categorized (labelled) or assigned any milestone. What should we do with it?

Is your test running OK, aside from seeing this warning message that applies to the location of the source code? Given that the NUnit tests are in the library and...

I'm guessing it's equal in the two cases but more visible in the TFS output. Since there is no use of the source in TFS, maybe we should skip the...

Maybe @osiristerje can try this (I'm traveling) and see. I think VS will give its own message if the source is not available. In the same way, the ide gives...

On the surface, it seems like we would want to fix this in 2.0.

Does the explorer window show the correct file location for the test method? If not, there may be something we can fix. But if it does, that means we are...

I have verified this behavior using the NUnit 3 adapter rather than NUnit 2, which seems to indicate it's just how it works with VS. The behavior makes a certain...