Option to create dump on test failure

[Evangelink]

Summary

It would be useful to be able to automatically create a dump on failed test/assertion. This is especially interesting when the issue is quite randomic and we are not having enough info to try to replicate the issue.

This should not be the default configuration but more an option that can be enabled. We could consider having some specific filter flag too to avoid launching the debugger on any failed test but rather on a list of tests.

cc @MarcoRossignoli @nohwnd

This relates to #2033 and could be handy for CI where launching debugger would be pointless.

[japj]

FYI, there are also some options in vstest to collect addtional information in case of test hangups: https://github.com/microsoft/vstest/blob/main/docs/RFCs/0028-BlameCollector-Hang-Detection.md

But I can imagine that creating a crashdump on an (assertion) failure needs to be done in mstest related code (instead of in vstest)

[Evangelink]

Hi @japj,

Thanks! We are aware of the crash dump and hang dump features of VSTest but as you pointed out this is a different suggestion that would create a dump on assertion failure and not test hang or test app crash.