Waiting for Test Controller

Question

I recently started working on getting Test Manager setup to run our automated Coded UI test scripts.

I followed the Essential Guide for running automated Tests from a Test Plan.

http://msdn.microsoft.com/en-us/library/ff472576.aspx

but after trying to run the test, it never starts running the test.  I stays in “Waiting for Test Controller”.

Here is some background.

We first setup a controller and a few agent machines. This was setup while we were developing the coded UI framework. We know that controller and agents’ setup worked since we were able to run our script from visual studio.

I then registered the controller to TFS.

I setup a lab environment and a couple of test settings

The Code UI tests were already version controlled.

We defined a build process and queued up a build.

I then continued to create a test plan and created a couple test cases and associated them to a couple of our code ui tests via Visual studio.

I assigned the build and test environment to our test plan.

At this point everything should be setup.

In Lab Center:

The Environment status = “Ready”

The environment has one desktop client machine with status = “Ready”

Testing Capabilities = “Ready”

In the Testing Center Properties section

                Builds:

Filter for builds: has the current build definition

Build in use: has the latest build selected.

                Automated runs:

                                Test Settings: has a test setting selected.

                                Test Environment: has the only environment I have setup selected.

So everything seems to be ready to run, so I go and run a test and the summary shows “Waiting for test controller” and it stays that way.

I check the the test run log by clicking “View” and it has nothing.

I read through http://blogs.msdn.com/b/aseemb/archive/2010/02/25/test-run-remains-in-waiting-for-test-controller-state-for-ever.aspx

And check rights and permissions with my TFS admin so everything seems to be good in the respect. All the machines (controller and agents) are online.

I even went and installed the Test Manager patch since it was also mentioned in comments section

http://support.microsoft.com/kb/2387011

 I read post http://social.msdn.microsoft.com/Forums/en/vsmantest/thread/3d2ee644-c8bb-4bc8-bc72-5a32622774cf

But the solution did resolve my issues.

I read post http://social.msdn.microsoft.com/Forums/en/vsmantest/thread/91298b51-eab4-493d-bafe-dfd1074f2cdb

But this issue is slightly different based on setup.

Answer 1

Hi ACortez,

Thank you for your post.

Seems  this case http://social.msdn.microsoft.com/Forums/en/vsmantest/thread/3d2ee644-c8bb-4bc8-bc72-5a32622774cf resolved the issue, thank you for sharing your experience. If I have misunderstood anything, please free feel to let me know.

Regards,

---

Lily Wu [MSFT]
MSDN Community Support | Feedback to us

Answer 2

Lily_Wu, 

Thanks for the reply, This is one of the first post that I read through and the answer didn't seem to help, but I am going to run through the post again, to see if there is anything I may have missed the first time.  I am also in the processing of setting up a couple of new Agents and I recently got a new Controller setup, so I am hoping the new setup with resolve the issues.

Thanks

Armando

Answer 3

Hi Armando,

Sorry for any inconvenience.

I saw following words, so i thought the issue is resolved. Sorry for any inconvenience again.

"I read post http://social.msdn.microsoft.com/Forums/en/vsmantest/thread/3d2ee644-c8bb-4bc8-bc72-5a32622774cf

But the solution did resolve my issues."

Regards,

---

Lily Wu [MSFT]
MSDN Community Support | Feedback to us

Answer 4

Lily,

QUick update, we finally figured out the issues last week on friday.

Issue 1, the Service Account that is running controller was not in the Project Collection Test Serivice Accounts group.  so that was the main reason why nothing whe happening when running the test, no error in the log.

Once we added the service account to the group, the test started to run and I finally started to see stuff in the view log file, but the test was now failing fairly quickly.

Issue 2, The service account that is running the controller did not have access to the build DIrectory.  I was getting the following error "Error starting the run: Build directory of this test run is not specific or does not exist."

found the following:
http://blogs.msdn.com/b/aseemb/archive/2009/11/25/error-starting-the-test-run-build-directory-of-the-test-run-is-not-specified-or-does-not-exist.aspx

Well we knew the build directory did exist so it has to be a rights issues.  After granting the service account user read rights to the build director, this error went away and we were finally able to run a few script successfully!!

 Thanks for you help!

Armando