To run some acceptance tests on my build server, I need to have a logged in user session open (the white testing framework needs to have a "screen" to test the WPF UIs) all of the time. This is obviously a fragile setup, and it introduces quite a bit of friction in our process.
Would it be possible to have a windows service running in the background that can then "spawn" a session that it logs into as a user, does some work (in this case the testing), and then log off? Or is there possibly a better way to handle my situation than what we're doing right now? It gets frustrating because, for example, if the application crashes at some point, the exception dialog box pops up, freezing our build server. I was thinking of disabling dr wastson to handle this, but I have this feeling that I'm going down a path fraught with peril.