When I ran the tests in previous versions of Test Studio for testing Visual Studio, and there is a problem, because of which there was a failure on failure (eg AccessViolationException, StackOverflowException, OutOfMemoryExceptionetc.), he gave a message display type of exclusion and inclusion of the magazine for more detailed information.
With Visual Studio 2017 Community Edition version 15.3.2 and .NET Core 1.0, when there is a failure, all that is shown in the test output:
[8/30/2017 3:03:42 AM Error] The active test run was interrupted.
[8/30/2017 3:03:42 AM Informational] =========== Test run completed: 1030 run (0: 41: 12.5762484) ==========
How can I determine what type of exception caused a crash during a crash (preferably with a stack trace)?
NOTE. . I uncovered a problem with NUnit during this investigation, asking how to determine which tests are causing the crash. I already isolated (and worked) 2 reasons.
But there is at least one more problem causing the crash. I am trying to understand why the test runner crashes in Visual Studio 2017, but not a command line crash.
Also note that this particular failure does not occur when working on the .NET Framework, so suggestions for using command line tools that do not support .NET Core 1.0 or .NET Core 2.0 (for example vstest.console.exe) do not help.