10

I have been having some problems with the test debugger in VS10. All tests are running without error, but when debugging it aborts when I try to read the object data. Afterwards, this error is displayed in the summary: Test host process exited unexpectedly.

I'm unable to see anymore details about the error. How do I access/generate test-log files? Or, even better: Has anyone experienced a similar problem? And found a solution?

Additional information:

The runtime-test-data is available on objects from same libary assembly, it's just one class I can't get access to in runtime mode. If I use breakpoints at:

  • every line that affects the object: - I can see the runtime-data and the test passes
  • only one place: - the test will abort and no data is visible
  • no breakpoints: - the test runs and passes.

The test used to work fine until recently. Just before the problem occurred when I made some solution changes with dividing the projects into solution folders. I didn't make any changes that should affect the code. Moving the projects back to their original folder don't solve the problem, So I wonder - Is this a bug in Visual Studio itself?

Here is what I've tried so far:

  • Rebuilding and cleaning the solution.
  • Closing Visual Studio and rebooting my system.
  • Installing VS10 Service Pack 1
  • Reinstalling Visual Studio 10
  • Testing on VS10 Ultimate and Premium
  • Removing and regenerating solutions files
  • Removing all break points
  • TraceAndTestImpact/Local.testsettings: Testing Timeout > timeout and setting abort to 30 minutes.
  • TraceAndTestImpact/Local.testsettings: Unit Test > Assembly folders defined
  • TraceAndTestImpact/Local.testsettings: Deployment > Enable deployment directories and files

How can I fix this? Any suggestions are welcome.

4444
  • 3,541
  • 10
  • 32
  • 43
Tinia
  • 205
  • 3
  • 9

4 Answers4

7

What's most likely happening here is that a property, local which is being evaluated in the locals or autos window is causing a side effect in the running process which leads to the failure. To verify this you should turn off automatic property evaluation

  • Tools -> Options
  • Go to the Debugger menu
  • Uncheck "Enable Property evaluation and other implicit function calls"
JaredPar
  • 733,204
  • 149
  • 1,241
  • 1,454
  • Thanks! That certainly stops the error from accouring. :) But it makes it impossible for me to debug the test, since I can't see any data. – Tinia Jul 26 '11 at 16:23
  • @Tinia, you can still debug here by explicitly evaluating the properties / functions which you need in the watch window. Simply type in the expression you care about and it will evaluate – JaredPar Jul 26 '11 at 16:24
  • The class in question is a class only containing data and data objects, no functions should be called to see the properties. Do you have eny suggestions to how I can locate this side-effect? – Tinia Jul 26 '11 at 16:27
  • 2
    The check box I had you disable will both auto execute properties and custom .ToString methods. There's no automatic way to figure out what's going on here. It basically comes down to evaluating them one at a time and seeing which one causes the problem. – JaredPar Jul 26 '11 at 16:28
  • Okay. Thank you very much :) Your answer was extremly helpfull :) – Tinia Jul 26 '11 at 16:34
  • 1
    And this is why debugger devs generally consider func eval evil: http://blogs.msdn.com/b/jmstall/archive/2005/03/23/400794.aspx I'm sure it drives them crazy to have to implement functionality in the debugger that can cause the process to become unstable (a reverse heisenbug?) – Michael Burr Jul 26 '11 at 18:37
0

I was finally able to resolve this issue in my case. What was happening for me was I was running asynchronous threads, but closed a process using a synchronous Close() method for a powershell runspace rather than the asynchronous CloseAsync() method.

Brandon Hawbaker
  • 534
  • 5
  • 5
0

Solution: It had overridden ToString, and as it showed out, there was a loop i forgot to close. After altering ToSting everything works fine.

Thank you very much for the answers :)

Tinia
  • 205
  • 3
  • 9
0

I was getting a similar issue, however in my case ALL tests were being skipped, and the error was reproducible on an empty test project, so code was ruled out.

Checking the EventViewer led me to the cause in my case; somehow the C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\QTAgent32.exe.config file had been removed from my machine?!? I copied one from another machine here and I'm back in action.

RJ Lohan
  • 6,497
  • 3
  • 34
  • 54
  • I'm getting this error if I create and run a new test project, but my QTAgent32.exe.config is there. I did, however, recently install .net 4.5. Maybe that has something to do with my problem. – Stephen Oberauer Sep 11 '12 at 10:21