Setting ServerGC for the test runner
See original GitHub issueDescription
VSTest.console.exe is currently configured to run in workstation GC (also concurrent). There is currently no way to change this behavior other than patching the vstest.console.exe.config
file in the VS installation folder. This solution is obviously not pleasant.
We have a big test assembly (11.5k tests) and it makes a big difference: the tests take 9 minutes to run with ServerGC=off
and 4.5 minutes with ServerGC=on
.
Expected behavior
- It’s probably not a bad thing to make
ServerGC=on
by default (MSTest v1 was using server GC, seeQTAgent32.exe.Config
) - If not, it would be nice to set the behavior via the
.runsettings
file.
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (10 by maintainers)
Top Results From Across the Web
Test Runner: CLI and Configuration
Web test runner looks for a configuration file in the current working directory called web-test-runner.config . The file extension can be .js ,...
Read more >Configure Test Studio Execution Server - Documentation
To start the Execution Client, called also Test Runner, type in the Windows Start Menu > Start Execution Server. Start Execution Server. The...
Read more >Test Runner: Dev Server
Web Test Runner is based on Web Dev Server and shares the same configuration. You can view the dev server documentation to learn...
Read more >Run manual tests - Azure Test Plans
Launch Test Runner from Azure Test Plans by selecting Run for desktop application from the dropdown menu. Screenshot shows launching the Test ......
Read more >Configure unit tests by using a .runsettings file
runsettings file. Select test settings file menu in Visual Studio 2019. The file appears on the Test menu, and you can select or...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ivonin my PR got merged, so this should be included in a future release & this can be closed 👍
@JoshKeegan some checks failed in my PR and to be honest I just didn’t have time to properly deal with it back then.
You can try again and see if maybe things have changed since.