.NET

1549 readers

2 users here now

Getting started

Useful resources

IDEs and code editors

Visual Studio (Windows/Mac)
Rider (Windows/Mac/Linux)
Visual Studio Code (Windows/Mac/Linux)

Tools

Decompilers: ILSpy, dotPeek
Scratchpad: LINQPad
Online playground and IL viewer: SharpLab

Rules

Rule 1: Follow Lemmy rules
Rule 2: Be excellent to each other, no hostility towards users for any reason
Rule 3: No spam of tools/companies/advertisements

Related communities

Wikipedia pages

.NET (open source & cross platform)
.NET Framework (proprietary & Windows-only)

founded 2 years ago

MODERATORS

erlingur

starman

Spyros

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.

you are viewing a single comment's thread
view the rest of the comments

[–] 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.