Support Test Explorer without C# Dev Kit

[kl-tie]

It is really shameful that we call .NET as free and open source framework and yet the toolings itself still not FOSS friendly, even such a basic and important features such as integrated testing like test explorer is not included in this extension and even it's also suggesting that we should use C# Dev Kit extension too while its license is actually still using the same license as Visual Studio.

Many programming language extensions such as Ruby LSP and Dart provides the test explorer integration for free without using restricting license as C# Dev Kit.

By comparing the outside .NET landscape like the above example, we can see that this should be a basic feature that included for free if we are still going to call .NET open source. I know this is a matter of toolings, but other FOSS languages still provide test explorer and it was backed up and maintained by big name maintainer such as Shopify. Either the test explorer should be included in this extension, or remove the VS license tied to C# Dev Kit, since at that point, it would be preferable to use Visual Studio instead since they have the same license.

[JustinGrote]

It would be nice I agree, but making these things costs a lot of money I assume and the test runner borrows closed source VS stuff just like parts of the LSP engine.

Microsoft.Testing.Platform, the new overarching test framework, is open source, so creating an extension to leverage this platform (C# dev kit tester already does), is feasible for the community to do.

[kl-tie]

It would be nice I agree, but making these things costs a lot of money I assume and the test runner borrows closed source VS stuff just like parts of the LSP engine.

Yes, making these things do costs money and time, but we can see the Dart and even Microsoft's own Python extension does include the test explorer for free 🤣.

Microsoft.Testing.Platform, the new overarching test framework, is open source, so creating an extension to leverage this platform (C# dev kit tester already does), is feasible for the community to do.

Interesting, but rather than creating another extension separated from C# extension, it would be better just to integrate it. That's why I asked to support the Test Explorer integration in C# extension, especially when we can use Microsoft.Testing.Platform instead of the supposedly proprietary one.