Marco Rossignoli

@StefanOssendorf out contributor @pape77 found a clever way to use merge with vstest, run tests sequentially and override merge one take a look maybe could help https://github.com/tonerdo/coverlet/pull/225#issuecomment-573896446

Thanks @bradwilson for the sample

> Yes that is how it currently works in VS with vstest, you send a full list of previously discovered tests to the runner to run them. In your case...

> That's an opinion, and not one that's shared by everybody. There are people who believe (and I am one of them) that if we discover 5 tests and then...

> We do that. I'm not sure why you think we don't. I need to do another check, I recall when I was running xunit tests suite that for one...

> So for my scenario: Test has a dependency Dependency fails My test may not have the correct state now, so it isn't run (but it was intended to be...

I think that TRX outcomes are more "extended" than the cases supported by VS for historical reason(AzDo support?) and predates VS? https://github.com/microsoft/vstest/blob/main/src/Microsoft.TestPlatform.Extensions.TrxLogger/ObjectModel/TestOutcome.cs @nohwnd @drognanar do you know if my assumption...

> It would also be nice if we allowed a reason / explanation for the results, same as there is a skipped result. We have the explanation for every state...

> For my framework, I have allowed tests to depend on other tests. If the dependency fails, I don't necessarily want to mark the dependent tests as failed, as that...

> To be fair it's fine if it's a successful state in my scenario, because the dependency test will report a failure anyway. I just didn't want all the dependents...