Youssef Victor

@OsirisTerje Let me expand more. Usually in MTP there is `TestMethodIdentifierProperty`. Currently we don't provide it in the bridge, and without ManagedType/ManagedMethod, we don't have a good way to provide...

@OsirisTerje So, to give a bit of history, Test Explorer used to use `FullyQualifiedName` to determine the source information for test cases. But this was never standardized, which makes it...

> You are aware that the naming of NUnit tests are much wider (in syntax) than what FQN will allow? I didn't dig into all the possible shapes of FQN...

If we will remove `vstestProvider`, then yes we expect these properties to be provided by NUnit. To be more precise, we expect it to be available at [this point](https://github.com/nunit/nunit3-vs-adapter/blob/204486c81ece7594d6b84b31eccfdbc6163c1886/src/NUnitTestAdapter/NUnit3TestDiscoverer.cs#L179).

Keep in mind that VSTestBridge will never add `TestMethodIdentifierProperty` if ManagedType/ManagedMethod are not available. So any extensions that will make use of `TestMethodIdentifierProperty` are not going to work with NUnit.

@marcpopMSFT Aspire doesn't use latest Arcade (they are sticking with Arcade 9 for now). That's why some targets had to be replicated, but we are aiming to simplify this once...

Strange. I can't see a possible relevant change between 5.0.0 and master https://github.com/nunit/nunit3-vs-adapter/compare/V5.0.0...master

It's all about whether you are executing all tests or selecting specific test(s) from Test Explorer.

Duplicate of #25

Hi @OnurGumus, @farlee2121, and @TheAngryByrd Let me clarify few points. --- > First, Microsoft.Testing.Platform doesn't respect `false`. `GenerateProgramFile` is a VSTest-specific property. If you want to disable the entry point...