2
votes

I'm running some automated Continuous Integration tests through a TFS build. The tests are written using the Microsoft UI Automation Framework on MSTest, and are configured to run locally on the build agent, without any controller or agent.

Now, the tests themselves execute well. The Startup method of the test suite launches the compiled application's executable and the process shows up in the server's task manager. However, since this is done through the Team Foundation Build Service, the UI isn't actually shown, as services are not allowed to interact with the active desktop.

Is there a way to force the application's UI to appear on the active desktop? I'm aware that I can install a test controller and agent that allow tests interaction with the desktop, however this creates additional overhead and some technical problems, as we're using VS2012 against TFS2010, which goes directly to the VS2010 MSTest and thus to the VS2010 test controller & agent, which I cannot configure through VS2012.

2

2 Answers

1
votes

I ended up setting up a test controller a test agent. Apparently, with VS2010 it's not possible to install a test agent on the same server with the build controller, so I went for a separate machine altogether.

The tests run nicely now!

0
votes

With what account are you logged on to the build server?

Only if you are logged on with the build account you will see the interaction with the desktop/UI.