I have a unit test suite using mstest that I can run fine inside Visual Studio, but when my deployment scripts try to run tests using the command line call to mstest, it will be frozen during the test for half the time. This is probably a problem in the test, but, unable to reproduce the problem inside the debugger, I could not find the problem.
So far, I have not been able to attach the mstest process in order to be able to debug the problem, because when I attach and pause, I see nothing in the visual studio (none of them are specified, no known code). Is there anything strange about how he uses applications that prevent him from easily joining him? Any other useful ways to try and troubleshoot, is it even possible to make the Console WriteLine equivalent from within the test so that mstest displays it in the console window in which it works?
source share