#vstest search results
Is there any way to automatically configure these options for everyone who opens the .sln? #visualstudio #vstest
Parallel Test Execution composition with the test framework, the test runner, and the test task [#MSTestV2, #VSTest, #VSTS]
![pvlakshm's tweet image. Parallel Test Execution composition with the test framework, the test runner, and the test task [#MSTestV2, #VSTest, #VSTS]](https://pbs.twimg.com/media/DWAo466UMAIEDB3.jpg)
dotnet test --collect "Code coverage" Preview shipped. In < 2 months since we published the RFC. [#vstest]
![pvlakshm's tweet image. dotnet test --collect "Code coverage"
Preview shipped.
In &lt; 2 months since we published the RFC. [#vstest]](https://pbs.twimg.com/media/Dfa9g5zU8AAEtFC.jpg)
Been working on perf of #vstest for a bit. Nice to see that "real-world" data show decrease in time. There are few more things lined up that will make this even better. But small steps. Each line is different test framework, and each point is 1 week of data averaged.
The #vstest and testfx (#MSTestV2) repos meet the recommended community standards. Thank you for your contributions till date, and keep them coming!
The Visual Studio Test Platform [#vstest] is now Open Source! github.com/Microsoft/vste…
github.com
GitHub - microsoft/vstest: Visual Studio Test Platform is the runner and engine that powers test...
Visual Studio Test Platform is the runner and engine that powers test explorer and vstest.console. - microsoft/vstest
the upside: it shows that #MSBuild and #VSTest are able to utilize the full power of the machine. but after the temperature of the machine stays > 70C for a few minutes and the load is still high then it understandably just throttles back. Still a laptop and not a workstation
Yet another step in improving #vstest performance - optionally skip initializing default adapters. See RFC here: github.com/Microsoft/vste…
Code Coverage support for .NET Core coming soon. Starting with Windows. RFC here: github.com/Microsoft/vste… [#vstest]
![pvlakshm's tweet image. Code Coverage support for .NET Core coming soon. Starting with Windows. RFC here: github.com/Microsoft/vste… [#vstest]](https://pbs.twimg.com/media/DaqkSnSVQAA9jqk.jpg)
Perf improvements coming to vstest: Pruning the set of assemblies given to test adapters. RFC here: github.com/Microsoft/vste… [#vstest]
![pvlakshm's tweet image. Perf improvements coming to vstest: Pruning the set of assemblies given to test adapters. RFC here:
github.com/Microsoft/vste… [#vstest]](https://pbs.twimg.com/media/DaqjD9_U0AEa_2U.jpg)
More perf improvements coming to vstest: Optimizing the set of adapters that are loaded and initialized. RFC here: github.com/Microsoft/vste… [#vstest]
![pvlakshm's tweet image. More perf improvements coming to vstest: Optimizing the set of adapters that are loaded and initialized. RFC here:
github.com/Microsoft/vste… [#vstest]](https://pbs.twimg.com/media/Daqj1Z3VAAAxkkq.jpg)
I've just published latest preview of vstest where we finally build against net8.0, please try updating and let us know if you find any problems. And see the release notes if you need to stay targeting net6. github.com/microsoft/vste… #dotnet #vstest #mstest #xunit #nunit
When you run dotnet test --arch x86, on a mix of test dlls that are AnyCPU, x64 and x86. #vstest #xunit #mstest #nunit #dotnet Do you expect: 1) All run, AnyCPU as x86, x86 as x86, x64 as x64 2) AnyCPU and x86 run as x86, x64 fails 3) AnyCPU and x86 run as x86, x64 skips
The dark blue line is a test framework that has no overhead of its own, so all the reported overhead is just #vstest overhead, ideally that would go down as close to 0 as possible.
Been working on perf of #vstest for a bit. Nice to see that "real-world" data show decrease in time. There are few more things lined up that will make this even better. But small steps. Each line is different test framework, and each point is 1 week of data averaged.
Test tools for .NET and cross-platform apps devblogs.microsoft.com/visualstudio/v… #VisualStudio #vs2022 #vstest
How to get code coverage with #vstest and coverage validator? Example shows .Net Core, but also works with regular .Net and Native (C++, C, etc). blog.softwareverify.com/code-coverage-… Video and step by step instructions.
Excited to announce that in collaboration with the #VSTest team at #Microsoft Coverlet is now supported out of the box with the #dotnetcore sdk. Using the "coverlet.collector" NuGet package, a simple: dotnet test --collect:"XPlat Code Coverage"; gets you most of the way there
I just discovered Balto, could be renamed tests-for-human #VSTest or #SublimeTests. github.com/Lothiraldan/ba… Thanks @lothiraldan youtube.com/watch?v=eAT0o4…
the upside: it shows that #MSBuild and #VSTest are able to utilize the full power of the machine. but after the temperature of the machine stays > 70C for a few minutes and the load is still high then it understandably just throttles back. Still a laptop and not a workstation
Great to see #VSTest to fix "dotnet test" on solutions by turning my comment from nearly a year ago into a PR 😃 github.com/Microsoft/vste…
Apparently, I cannot do any patch releases of @fsharpMake 5 because people keep adding new features. Thanks everyone. 5.3 will be out soonish. People added support for #RSync #WiX and #VStest and a couple of bug-fixes :)
Retweeted Pratap Lakshman (@pvlakshm): vstest v15.8.0 RTMs with support for code coverage for .NET Core (via portable PDBs). Download: nuget.org/packages/Micro… Release notes: github.com/Microsoft/vste… [#vstest]
vstest v15.8.0 RTMs with support for code coverage for .NET Core (via portable PDBs). Download: nuget.org/packages/Micro… Release notes: github.com/Microsoft/vste… [#vstest]
Is there any way to automatically configure these options for everyone who opens the .sln? #visualstudio #vstest
the upside: it shows that #MSBuild and #VSTest are able to utilize the full power of the machine. but after the temperature of the machine stays > 70C for a few minutes and the load is still high then it understandably just throttles back. Still a laptop and not a workstation
Parallel Test Execution composition with the test framework, the test runner, and the test task [#MSTestV2, #VSTest, #VSTS]
dotnet test --collect "Code coverage" Preview shipped. In < 2 months since we published the RFC. [#vstest]
Been working on perf of #vstest for a bit. Nice to see that "real-world" data show decrease in time. There are few more things lined up that will make this even better. But small steps. Each line is different test framework, and each point is 1 week of data averaged.
The #vstest and testfx (#MSTestV2) repos meet the recommended community standards. Thank you for your contributions till date, and keep them coming!
Code Coverage support for .NET Core coming soon. Starting with Windows. RFC here: github.com/Microsoft/vste… [#vstest]
Retweeted Pratap Lakshman (@pvlakshm): More perf improvements coming to vstest: Optimizing the set of adapters that are loaded and initialized. RFC here: github.com/Microsoft/vste… [#vstest]
Yet another step in improving #vstest performance - optionally skip initializing default adapters. See RFC here: github.com/Microsoft/vste…
Perf improvements coming to vstest: Pruning the set of assemblies given to test adapters. RFC here: github.com/Microsoft/vste… [#vstest]
More perf improvements coming to vstest: Optimizing the set of adapters that are loaded and initialized. RFC here: github.com/Microsoft/vste… [#vstest]
Something went wrong.
Something went wrong.
United States Trends
- 1. Bama 17.1K posts
- 2. Oklahoma 26.2K posts
- 3. Ty Simpson 3,622 posts
- 4. #UFC322 30.5K posts
- 5. BOOMER SOONER 1,771 posts
- 6. Iowa 19K posts
- 7. Mateer 3,043 posts
- 8. Jungkook 246K posts
- 9. Brent Venables 1,049 posts
- 10. #RollTide 3,177 posts
- 11. #EubankBenn2 30.3K posts
- 12. South Carolina 33.6K posts
- 13. Kline 1,558 posts
- 14. DeBoer 1,336 posts
- 15. Heisman 10.6K posts
- 16. Ryan Williams 1,701 posts
- 17. Arbuckle 1,047 posts
- 18. Talty 1,592 posts
- 19. Georgia Tech 2,649 posts
- 20. Sabatini 1,086 posts