xUnit.netMicrosoft.Testing.Platform v2 support is now available in a prerelease CI build. Note that we will continue to support v1 by default; you must opt into v2.
More information: https://github.com/xunit/xunit/issues/3416#issuecomment-3447785145
nietras πΎNew dotnet test experience for Microsoft.Testing.Platform.
Brandon H 
via @dotnet : Enhance your CLI testing workflow with the new dotnet test
https://ift.tt/Yp23zum
#dotnet #dotnettest #CLITesting #MicrosoftTestingPlatform #MTP #VSTest #NUnit #xUnit #MSTest #TUnit #TestingWorkflow #SoftwareTesting #DevOps #ContinuousIntegration #β¦
via @dotnet : Microsoft.Testing.Platform: Now Supported by All Major .NET Test Frameworks
https://ift.tt/Y5EOJMG
#MicrosoftTestingPlatform #DotNet #TestFrameworks #MSTest #NUnit #xUnit #Expecto #TUnit #OpenSource #DevCommunity #ContinuousIntegration #TestingEcosβ¦
Microsoft.Testing.Platform: Now Supported by All Major .NET Test Frameworks - .NET Blog
All major .NET testing frameworks are now supporting Microsoft.Testing.Platform. Whether you are using Expecto, MSTest, NUnit, TUnit, or xUnit.net, you can now leverage the new testing platform to run your tests.
Do you think it's weird that v3 test projects are stand-alone executables? You're not alone. Here is a brief history behind the decision.
https://github.com/xunit/xunit/issues/3139#issuecomment-2611568692
Build error in xUnit 3 test projects targeting full .NET Framework Β· Issue #3139 Β· xunit/xunit
I encountered this issue while migrating the code of AutoFixture.xUnit2 to xUnit 3 (as mentioned in AutoFixture/AutoFixture#1471 (comment)). The test project was targeting a couple .NET versions in...