There is no test with specified Id

I’ve been struggling with this error in Microsoft Coded UI / Team Foundation Server / Test Manager 2010 for a few days.  Our automated test cases are manually created, checked into TFS, and built by MS Build.  We’re using Microsoft Controller / Agent to direct test runs on virtualized machines (Hyper-V).

That’s all fine and dandy (and it works).  But now, we want to drive the automated tests with Microsoft Test Manager.  We set up the Lab Management environments, ensured that the Controller and Agents appear, that the build is copying the DLLs correctly.  But when we choose “run with options”, and select the appropriate build, we are slapped with the following error:

This one stumped me for a few days.  My diligent build manager worked with me tirelessly to ensure that the DLLs were included in the build, and even that the Controller could see them.  But there was no good information on why it couldn’t find the Test Case.  In our architecture, Test Cases are methods in a Coded UI project, with data-driven XML inputs, multiple UI Maps, custom attributes, lots of internal references to our main Office application, and …

Well, let’s just say it’s a tad more complicated than your run-of-the-mill recorded, web-based IBuySpy application.  The only other good information we could find about it was on Alkampfer’s Place:

Unfortunately, our situation was a bit more complex.  The resolution, as it turned out, had to do with how we were linking Test Cases with our “Associated Automation” in TFS.  We had restructured our namespace a few months previously, and completely neglected to update the Associated Automation path:

So, the bottom line is if you encounter the error “There is no test case with specified Id {GUID}”, please also check that your Associated Automation Automated test name is correct.

This entry was posted in Microsoft Test Manager. Bookmark the permalink.

One Response to There is no test with specified Id

  1. Cameron Flint says:

    Thanks, Phillip! This solution directed me straight to the problem and saved quite a bit of time. It’s worth pointing out that in my case I had to fully remove the association and re-add it to resolve the error.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s