vstest
Visual Studio Test Platform is the runner and engine that powers test explorer and vstest.console. (by microsoft)
coverlet
Cross platform code coverage for .NET (by coverlet-coverage)
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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
Posts with mentions or reviews of vstest.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-06-14.
-
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.
coverlet
Posts with mentions or reviews of coverlet.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-27.
-
Setting up a simple testing project with C#
You might have noticed when you were looking in NuGet, there was a package called coverlet installed into the project:
-
Do you use any code coverage tool on your project?
There are a lot libraries to collect code coverage, one of this one is Coverlet: https://github.com/coverlet-coverage/coverlet
-
Code Coverage for Build Server without Visual Studio Enterprise
We use Coverlet. You have to do some work to get it working with your tests but I have no complaints. I don't know for sure if it works with VS Community, but since it plugs into MSBuild I'm not sure how it could be gated to that.
-
How to define the same folder for merging test coverage?
And I would like to build a total test coverage for the solution. So, I added coverlet.msbuild to the dependencies and executed the next command from the examples of coverlet
-
Analyzing and enforcing .NET code coverage with coverlet
CoverletOutputFormat: The format of the report that coverlet will generate (opencover, cobertura, json). More here;
- Code coverage and warnings for modified files only
-
Generating Code Coverage Metrics for .NET Framework Applications
Utilize Coverletand Report Generator utilities – however, this is where its funny, because these are .NET CLI tools that need the .NET 6 SDK installed.
-
Code coverage for Asp.net 6 web APIs
Coverlet works really well.
-
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.
-
Code Coverage Tool For XUnit
Coverlet