this post was submitted on 13 Feb 2025
4 points (100.0% liked)

.NET

1549 readers
2 users here now

Getting started

Useful resources

IDEs and code editors

Tools

Rules

Related communities

Wikipedia pages

founded 2 years ago
MODERATORS
erlingur
starman
Spyros
4
Microsoft.Testing.Platform: Now Supported by All Major .NET Test Frameworks - .NET Blog (devblogs.microsoft.com)
submitted 1 week ago by Kissaki to c/dotnet
2 comments fedilink hide all child comments
 

Whether you are using Expecto, MSTest, NUnit, TUnit, or xUnit.net, you can now leverage the new testing platform to run your tests.

In this post, we’ll highlight the test frameworks that have embraced Microsoft.Testing.Platform, share their unique characteristics, and provide resources for getting started.

top 2 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 1 week ago (1 children)

@Kissaki It's not obvious to me from either the Microsoft announcement or the XUnit announcement here: https://xunit.net/docs/getting-started/v3/microsoft-testing-platform

So... Is there any benefit to me, as a developer, right now, to using the new testing platform over the old?

[–] Kissaki 2 points 1 week ago

I think it simplifies setup because you only have to set the SDK, not include runner dependencies? I think it's also more performant and may have different console output? (I think I read that before, but not sure anymore.)

At work I migrated all unit test projects to the new system. IIRC mainly because it's a FOSS solution and forward-facing, and a simplification of dependency/project setup.

I can't give you anything concrete though. In the MS blog post they label it an alternative. You're fine to stick with VSTest for now, without significant downsides.