File extension specified '.aii' is not a valid test extension.

Hi Nuno,

This was a problem we found and fixed last year. Is Visual Studio installed on the machine along with Test Studio 2011.1.502? Support for running tests in MTM won't be installed if VS is not detected on the machine.

Greetings,
Cody
the Telerik team

Hello Cody,

Thanks for the quick reply.

Yes, our build server has VS2010 and Test Studio 2011.1.502 installed.

We have the build server with a test controller and test agent since it was the only way to have TCM executing aii files with code on a remote machine.
(I don't know if you still remember we had that issue some time ago).

What can be causing this issue ?

Thanks Cody,
Nuno

Hi Nuno,

Yes I remember the original report (all too well as I was the one that worked with Microsoft to get to the root cause originally). I think the best thing is to look at this problem on the build/test machine via GoToMeeting. When is a good time?

All the best,
Cody
the Telerik team

Hi Cody,

Sorry for my delay, I just returned from vacation.

Any time you want is good for me. Today? What time?

Thanks,
Nuno

Hello Nuno,

Just letting you know I haven't forgotten you or this problem. I just finished setting up TFS 2010 along with VS 2010 on a test machine. i am now proceeding with trying to replicate the problems.

Regards,
Cody
the Telerik team

Hi Cody,

Thanks for the update.

Let me know if you need any details on how I set up our testing environment, if that helps you.

Regards,
Nuno

Hi Dennis Perlot,

I sent you and Nuno an update via email yesterday. Let me know where you want to go from here.

All the best,
Cody
the Telerik team

Hello Cody,

I just watched the recording you kindly provided.

It looks like there are three differences between our scenarios:
- We are testing a SL App
- We have tests with coded steps
- (Once tests run on the same machine) It is our goal to have the test agent in different machine (not the build server)

Please, let us know how was it after matching our scenario and running the tests again.

By the way, what's the settings for your MTM environment "aotvm2-tfs2010" ?

Thank you for your effort!

Kind regards,
Nuno

Hello Nuno,

I added coded and Silverlight tests to the test project and test plan. Didn't run into any problems as you can see in this new video. You may notice that test 3 failed, but I'm not concerned as to why it failed at this point. You can see that the coded step in it ran just fine, and it also nicely proves MTM will see and log failed tests correctly.

I included a screenshot of my MTM Lab setup. I hope that answers your question regarding configuration.

Best wishes,
Cody
the Telerik team

Hi Cody,

Thanks for the screenshot, it tells that our environment settings do match.

The only outstanding difference now seems to be the Test Studio version, we are using version 111.5.2.0 .

Might that be the reason? Could you please try using that version?

Thank you,
Nuno

Hi Nuno,

We don't have a version "111.5.2.0" Can you re-specify which version? Then I'll try it.

Best wishes,
Cody
the Telerik team

Hi Cody,

Windows "Programs and Features" show version 111.5.2.0 is installed as you can see in the attached image... It refers to version 2011.1.502.0.

Thank you for giving it a try.

Regards,
Nuno

Hi Nuno,

I am sorry, I forgot about the awkward version number displayed in Programs and Features. It doesn't allow number greater than 125 in the Major field so we opted for the mangled numbering scheme as an alternative.

test Studio 2011.1.502.0 is known to have many serious flaws. I highly recommend going to our latest internal build, 2011.1.809 instead. It is much more stable (and has a few new features also).

I did run the same set of tests on 2011.1.502.0 (though I had to re-record new ones because tests made in 2011.1.809 are not backward compatible). They all ran successfully, just like using Test Studio 2011.1.809.

Best wishes,
Cody
the Telerik team

Hi Cody,

Telerik documentation advises not to use internal builds in production environments but I'm giving it a try at least to see if it runs the tests...

I'll keep you informed.

Thanks,
Nuno

Hi Nuno,

I admit our internal builds are not as thoroughly tested as our major and service pack released. 2011.1 712 is our last service pack release and is quite stable. Also our latest internal build of 2011.1.809 has proved to be quite stable. Our official statement is use internal builds when you must overcome a bug, but be aware they have had a minimum of QA testing.

I look forward to hearing your test results.

Best wishes,
Cody
the Telerik team

Cody/anyone else at Telerik,

My apologies for reviving a thread which is almost a year old - but was this problem ever resolved?  If so, what was the solution?

I am asking because I am seeing the exact same error under the same circumstances but on a much more recent build (2012.1.411.0).  Here is the background ...
 
I am trying to set up a second test server to run Test Studio UI tests in a TFS/MTM environment (VS2010) - we are doing this as part of a POC for trying out a multiple test server environment.  The second test server has the following:

VS2010 Ultimate
TFS 2010 with Build Controller and Agents
Visual Studio 2010 Test Controller
Visual Studio 2010 Test Agent
Test Studio 2012.1.411.0 (full package, trial license)

I also have created a test plan in MTM whose test settings and test environmnent settings point to the new server.  Finally, I have activated the trial license both in stand-alone and from VS2010.

When I try to run a test from this test plan, it Errors out with the same error message reported by the OP.

We already have one test server which is working fine - its configuration is identical except that it is running the Test Studio Runtime environmnent (same version).  I installed the trial version of the full product on the second server as we currently have only one license of the runtime (we plan to puchase a second license if this POC is successful). 

Any ideas on what could be causing the issue - and what I can try to resolve it?  Could it be that I have the trial version installed - does it need to be a licensed version of the full software?  If not, what else might be the issue?

I hope you won't ask me to upgrade to the latest version as the first troubleshooting step - first of all, we have one server running under the old version and it is running file (that tells me that software version is very likely not the reason for this issue).  Second, we cannot upgrade without a full test against our current code - past couple of attempts to upgrade have been aborted because of serious problems encountered in our tests under the new version.

I look forward to hearing your suggestions.

Thanks,
Shashi

Hello,

A response to this would be much appreciated ...

Thanks,
Shashi

Hi Shashi,

I apologize for the delay responding back to you. The error message "File extension specified '.aii' is not a valid test extension." is always tough to troubleshoot and fix. Microsoft build and test controller setup is something of a mystery why/how/when it works and doesn't work.

What we do know is that Test Studio (either full edition or Run-Time edition) must be installed on your Test controller and your Test agent for it to work. Sometimes you have to unregister and re-register your Test controller before TFS/MTM recognize that Test Studio has been installed on it.

One way to diagnose where the problem lies is to try to manually run tests via MSTest from the command line. First try running a Test Studio test on the Test controller. If that succeeds try running it on the Test agent. You will get the same error message if there's a problem with the Test Studio installation/integration for that machine.

All the best,
Cody
the Telerik team

Hi Cody,

I got it to work!  One of your suggestions - while not the solution itself - led me to it.  You had said the following:

Sometimes you have to unregister and re-register your Test controller before TFS/MTM recognize that Test Studio has been installed on it.

Instead of registering and unregistering it, I simply stopped and restarted the test controller and then the test agent (which were both on the same server).  That did the trick ...  I then ran into another issue (where the test wouldnt type into the page - but that got resolved after I configured the browser for running tests per your instructions.  I am now able to run one of our basic tests (Login) completely and it passes.

I think the problem was that I had installed TS after I configured the controller and agent - and so the latter did not know about TS until I restarted them.  If you have any instructions to set up a MTM environment with Test Studio anywhere on your site or in the Help - you may want to add this step to that  document ...

Thanks again for your excellent (as always) help ...

Shashi

Hello Shashi,

That is great news! Thank you for the update. Yes, installing Test Studio while your Test Controller is already configured and running will require you to at least restart the service. It only picks up on the registered test types during controller initialization, done once at startup.

We'll add your solution to our KB articles.

Greetings,
Cody
the Telerik team