So the real challenge I faced was getting MTM to work with the test controller in domain DEV. Make sure you install SP1 of Visual Studio 2010 here as well, since that includes some important patches for your controller and agent infrastructure.

I run the build controller under a custom domain service account and gave it the appropriate rights (place them in the specially created admin groups). So what are the problems I ran into and how where they solved?įirst of all, getting the Test controller up and running on the build server was easy, just install the Visual Studio Test Controller 2010 as found in this download. This server also runs in Domain DEV, same as our Database Server. My test server is running IIS and is the web server of our web application. I have my test controller running on our build server, since that machine doesn’t have to do anything most of the day. So I am the blue guy trying to do some work in MTM (especially automating my test runs) and I work from Domain PROD To give an overview on the basic setup of this environment: In such an environment, you might hit some roadblocks. To give some context, MTM and the test agents work great if you work in a simple domain configuration, but I work in an environment where there is a set of active directory domains and trust relationships. The past few weeks I was challenged on my current project to get an environment set up that works well with Microsoft Test Manager (MTM).

Download visual studio test manager