Thursday, March 25, 2010 6:59 PM
In the Microsoft Test Manager UI, I have configured my test plan with specific 'Test settings' and a 'Test environment' for automated test cases. The environment is configured to run the test cases using remote test controller and test agent machines.
When I run a test suite from the UI using the configured test settings and environment, the test case is executed successfully.
When I attempt to execute the same test suite using from the tcm.exe command line utility (without specifying the /testsettings or /testenvironment command line arguments), the run is created. However, upon viewing the test results in the Microsoft Test Manager UI, I see that the test run has aborted. Upon looking at the test run, I see that the 'Test settings', 'Test environment' and 'Test controller' attributes are all displayed as expected.
However, when I check the 'Test Run Log' I see the following:
Unexpected error occurred. Aborting run: The test controller for test run 31 does not match the test environment being used. Make sure the test run uses the same test controller as the one associated with the test environment.
Any ideas on what I might be doing wrong?
Friday, March 26, 2010 2:11 AM
I tried your scenario as you specify it and what i saw is that the test settings are not picked up from the plan.
If you specify the test settings, then it should work.
I will report this issue and hopefully it can be fixed at some point, although this won't make it into this release.
VS Team Test
Friday, March 26, 2010 1:58 PM
Once I figured out what to use for my test environment name on the tcm utility command line, I was able to get my test suite to run.