CharliePoole

Perhaps, but definitely not in our control.

@OsirisTerje can you try? They don't talk to me for sure.

Thanks @OsirisTerje If this turns out to be something they don't expect to change anytime soon, I think we should just close it as not our bug.

If it's a problem in the v2 adapter, then it belongs here. If other people have a problem on v3, we may need a separate issue.

Understood. My comment was meant to reflect my disagreement with that policy.

@OsirisTerje Seems like we would fix this if confirmed. Do you disagree?

The bug under the NUnit 3 adapter was never actually worked on, which is why there is no code pointed to. Rather, there were a lot of changes going on...

If that's true, it seems like it must be a Test Explorer rather than an adapter bug. The adapter only starts discovery when it's called by VS.

On the other hand, we think it was resolved for the NUnit 3 adapter due to some change made. Hmm...

In order for us to know how to treat this report, we need to know the signature of the test that is not known to Visual Studio. If it's a...