Marco Rossignoli

Add `Threshold` feature to vstest collectors integration

2

Today with .net tool/msbuild you can specify a coverage threshold below which it fails the build. https://github.com/tonerdo/coverlet/blob/master/Documentation/MSBuildIntegration.md#threshold This is not supported on vstest collector integration cc: @vagisha-nidhi

Current architecture is creating the push node for the out of process extension before the main on in the test host. This lead to some custom code inside VS to...

Ref https://github.com/microsoft/testfx/issues/3478#issuecomment-2315852176

Closes https://github.com/microsoft/testfx/issues/3716

Add `VSTestBridge` msbuild capability for VS and runsetting handling

2

We should announce to VS if pass or not the runsetting. If adapter is using the `VSTestBridge` it's handled automatically, otherwise is ignored. ~~This means rename also the `--settings` to...

VS doesn't honor the `None` logging level when used with the Testing platform.

use `ValueTask` instead of `Task` if possible

2

For compat reason we're returning from the API `Tasks` we could have some performance benefit (expecially for the `IMessageBus` `IDataConsumer`) if we move it to `ValueTask`.

Allow custom --help output

2

It could be useful give a way to the users to customize the UX for the `--help` command. We already allow to have * custom banner * custom output device...

We should make all the built-in payloads that we can push inside the message bus immutable by default. Ref https://github.com/microsoft/testfx/issues/3242

When https://github.com/microsoft/testfx/issues/3355 will be completed we should review the exposed extension and where we need the session id or the cancellation token we should simplify the api using the new...