title: How to handle failed asserts and abort calls with Microsofts unit testing framework?
body: <p>I just moved from my catch2 testing frameworks to Microsofts native code C++ unit testing framework for the nicer integration into the IDE. </p>
  
  <p>But my coding style is to use lots of assert statements all over the code. I cant replace them with macro calls like AssertIfTrue calls without poisoning the whole codebase with dependencies to the framework. </p>
  
  <p>But if an assert fails the unit test runner stops with message box popup and when i press abort button the test will be reported as skipped and not as failed. This also looks like impossible behaviour for any automated continuous integration lifecycle. </p>
  
  <p>I already tried setting a signal handler via <code>signal(SIGABRT, SignalHandler);</code> but the handler is never called. And using _set_abort_behavior to disable the message box with  <code>_set_abort_behavior( 0, _WRITE_ABORT_MSG);</code> also has no result.</p>