Youssef Victor

Looking at the stack trace. `CommonTestHost.RunAsync` already handles `OperationCanceledException` when `testApplicationCancellationToken.IsCancellationRequested` is true. So, based on this stack trace, we got `OperationCanceledException`, but `testApplicationCancellationToken.IsCancellationRequested` wasn't true. The `WaitConnectionAsync` call in...

@nohwnd I'm not sure if this SerialConsoleLogger -> ParallelConsoleLogger is related to the race you are investigating with VSTest terminal logger, but thought it's worth noting this to you :)

Issue mentions that Ctrl+C works when parallelization is disabled, but not with enabled. This is likely suggesting an NUnit bug and probably unlikely to be an issue on MTP side...

Thanks for reporting this @johncrim. I do agree that the documentation can be improved here. There are not much testconfig.json options for the core platform though, and most are for...

Thanks for the feedback @alexTr3. Please make sure to follow [Code of Conduct](https://github.com/microsoft/testfx/blob/main/CODE_OF_CONDUCT.md). To answer your questions: > added Microsoft.Testing.Platform.MSBuild reference to my project and it does not even rename...

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

> 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...

Parallelization inside of a single test assembly is not controlled by IDE, dotnet test, VSTest, or Microsoft.Testing.Platform at all. This is a feature of the **test framework** (e.g, MSTest, NUnit,...

> TestingPlatformCommandLineArguments is not working when running tests in visual studio 2026 > > tested with "maxParallelThreads": 1.. and multiple thread starts.. I assume you use xunit.v3, as the `maxParallelThreads`...

For reference, https://github.com/microsoft/vstest/issues/4657 suggests that this used to work.