Alexandre Trepanier

I'm currently facing this issues in CI, is there any quick fix? Test are running locally but not in linux CI / google cloud build and facing the same error...

This is an awful bug that need to be fixed ASAP! Please release a patch with just this bug fixed!!! ASAP Oh sorry about that it seem to be currently...

awful release.. added Microsoft.Testing.Platform.MSBuild reference to my project and it does not even rename the testconfig.json! I tried both in a core library (test) and in the executable test project...

ok so I understand why it's not working, you need to have a copy of the testconfig.json in every executable test project. you cannot have it in a core library...

My advice.. make an example solution of each framework version (vstest vs mtp etc..) for each test platform (xunit) etc.. and each configuration..(testconfig, testrunner) etc.. so one can easily see...

I understand that you can add the testingplatformcommandlinearguments but .. you should support having the testconfig.json file in a core library and core library should be supported like in any...

so I repeat if I use the the TestingPlatformCommandLineArguments in Directory.Build.props will it be used when I run tests in visual studio IDE?? what config file is used when I...

I want to run test in parallel so that dropdown is useless to me.. I have 32 threads, I want these threads to be used on the first test project...

TestingPlatformCommandLineArguments is not working when running tests in visual studio 2026 tested with "maxParallelThreads": 1.. and multiple thread starts..

--max-parallel-test-modules is only from commandline ? can I have the same thing when running tests in visual studio?