You may have noticed that one library, Terminaux, had its unit test project improved. How? By using the newly introduced SDK, called MSTest.Sdk. According to this Microsoft blog post, it has several improvements over the older style that we’re migrating all our test projects from, such as:
- Better defaults
- Simplified usage
- Extensibility of the MSTest runner
- Easier opt-in for new features (e.g., native AOT tests).
This new SDK not only boasts better default configurations, such as increasing your required MSTest.Sdk version at the top of your unit test .csproj file, but it also simplifies the definition of the project file itself by implicitly referencing the required MSTest NuGet packages using the version defined in the SDK definition, extends the MSTest runner, and letting you opt in to the new features easier than before, such as the native AOT tests.
Our libraries will slowly migrate to use this testing style, ensuring that we have no intention to use any other test framework, such as NUnit (which we have used previously) and xUnit. This will bring improved testing performance, as well as improved testing reliability.
However, this means that in order to be able to build our projects that have been migrated to use the new SDK, you’ll have to upgrade Visual Studio to at least 17.9.
Enjoy!
Aptivi 
Thoughts?