yeah right :)
ok Step by step
open 2 VS (one with the app solution and one with the test solution)
set breakpoint in test after application launches and debug the test. The tests wait and the application has started => right?
set breakpoint in the app under test and attach debugger to running app.
now continue with test execution
Hi ... thx .. but
All projects, both production and test, are in the one solution. Having two solutions is something to consider but not desirable. We run our tests from within Visual Studio's IDE using Resharper. Want to run the test in debug mode with VS Debug | Excpetions
break on all set so that when an exception occurs VS shows the line immediately. Nice, simple, fast. I want to get team member acceptance.
Thing is we do not feel any need to test, in all tests, that Windows can launch an EXE. So if we could open the main window in the running test application then all would be good in the world. But I hit the problem of giving CPU time to the window. Can do
up to the point of calling UIItem.Click. I've tried adding a wait handler but that just does not do it.
If I can do this I can run all our UATs, not as a separate app, but as a window from the test app. Faster (was when I did this on WinForm apps) and easier to debug.