Tom Longhurst

Here's a current VSTest NUnit repro: ```csharp [TestFixtureSource(typeof(Base), nameof(Base.All))] public class ClassDataSourceDrivenTests2 { private readonly Base _base; public ClassDataSourceDrivenTests2(Base @base) { _base = @base; } [Test] public void Base_Derived1() {...

I've tried setting the `TypeName` in `TestMethodIdentifierProperty` to more of a display name. That sort of works, but doesn't give you the same level of organisation of being able to...

Thinking about this further, it'd be good to allow the framework to have full control over how tests display in test explorers. I think the best way to allow this...

In the existing NUnit example above, there's also differences between how Rider and Visual Studio display these. I think it's better to give this control to the testing framework rather...

Feel free to send them this ticket if it'll help persuade them! Currently the test explorer makes assumptions about how to organise tests. Different frameworks may have different intentions so...

Thanks for replying @Evangelink ! Completely agree with you. Hoping @MarcoRossignoli can throw some weight here too and maybe make this a possibility. At work we have a multi-tenanted solution,...

Also, you guys mention that the testing explorer is owned by another team, which I completely appreciate, but visual studio isn't the only testing explorer out there as you know,...

Don't suppose there was any discussions with the test explorer team since the last comment? cc. @MarcoRossignoli

Just to provide more scenarios/context: Namespace > Class > Inner Class > Inner Inner Class > Test Maybe not the most conventional but a clear example of a use case...

I've raised this for the VS team: https://developercommunity.visualstudio.com/t/Allow-test-frameworks-to-control-the-tes/10889052