vstest
List-of-Testing-Tools-and-Frameworks-for-.NET
vstest | List-of-Testing-Tools-and-Frameworks-for-.NET | |
---|---|---|
5 | 1 | |
858 | 513 | |
1.9% | - | |
9.5 | 5.5 | |
5 days ago | 3 months ago | |
C# | C# | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vstest
-
Pressing CTRL+C while reading user input (Console.ReadLine) has a weird issue.
Another commenter in your first post linked you to a bug report. The original bug was a sporadic one with dotnet test. But commenters added more reliable cases, and cases for other dotnet commands.
-
Why does VSTest put the output of data collectors to GUIDed subdirectories?
However, I am hesitant to do so. Whenever it seems I have to fight the tools that are provided for me this is a likely sign that I’m Doing Things Wrong because of some fundamental misunderstandings and misassumptions on my part. I did some digging and found that VSTest by design forces the placement of data collectors’ output into GUIDed subdirectories, see Coverlet documentation, Coverlet issue #500 and VSTest issue #2378. That this is forced by design reinforces my worries that I’m doing something counterproductive.
-
Integrating VSTest
I've had success creating my own logger by following this guide on the vsdocs github. Nowadays you don't have to deploy the assemblies for the custom logger to the vs install folders. vstest will scan the build output directory for assemblies that match the specified pattern, *.testlogger.dll. You can also specify the path for custom test adapters either from the command line or a runsettings file using the TestAdapterPath option (this is only available since v15.1 but you mentioned you've tried the html logger and I think that's much newer than v15.1). If you get stuck with the implementation you can try referring to vstest's own loggers: htmllogger, trxlogger.
-
Pick your class
IMO it's just held back by its ecosystem. NuGet doesn't integrate nearly as well with library source as Maven/Gradle/etc, and stuff like this makes it feel like a second-class citizen for CI.
-
Banging my head against a wall, any one here ever get intimate with Microsfot.NET.Test.SDK?
But going to have to dig in deep tonight, it seems that answer to what I seek is probably hidden somewhere in this repo: https://github.com/microsoft/vstest/ and the ITestDiscovery discovery process.
List-of-Testing-Tools-and-Frameworks-for-.NET
-
Proper Rest API Load Testing
Here a list of testing tools for dotnet: https://github.com/dariusz-wozniak/List-of-Testing-Tools-and-Frameworks-for-.NET
What are some alternatives?
MSTest - MSTest framework and adapter
System.IO.Abstractions - Just like System.Web.Abstractions, but for System.IO. Yay for testable IO access!
FlaUI - UI automation library for .Net
Fluent Assertions - A very extensive set of extension methods that allow you to more naturally specify the expected outcome of a TDD or BDD-style unit tests. Targets .NET Framework 4.7, as well as .NET Core 2.1, .NET Core 3.0, .NET 6, .NET Standard 2.0 and 2.1. Supports the unit test frameworks MSTest2, NUnit3, XUnit2, MSpec, and NSpec3.
qest - A simple, cross platform, command line tool to test MSSQL procedures
Ogooreck - Sneaky Testing Library in BDD style
Fine Code Coverage - Visualize unit test code coverage easily for free in Visual Studio Community Edition (and other editions too)
ITimer - Provides a testable abstraction and alternative to System.Threading.Timer and System.Timers.Timer. Targets netstandard2.0 and higher.
coverlet - Cross platform code coverage for .NET
graphql-to-karate - Automagically generate Karate API tests from your GraphQL schemas. Useful for test-driven development, change validation in CI/CD, and more.
Tyrannoport - 🦖 For processing TRX files into something more enjoyable 🦖
vs-clove-unit - CLove-Unit Test Adapter for Visual Studio