How to specify the build directory of a test run (using Microsoft Test Manager)

2
votes

I am trying to run automated coded UI tests using Microsoft Test Manager, but I am getting the following error message in the test run log entry:

"Error starting the test run: Build directory of the test run is not specified or does not exist"

I already have a build assigned to the test run.

And I don't see how it can't find the build directory as I'm attempting to launch the tests from the build machine.

Edit: Perhaps a fake build can be created that I can link the tests to? How can this be done?

Update: I added the test project to the build, and re-associated the test case with the ordered test list, then created another build. I ensured that the build was output to the correct location, C:\GatedCheckinBuild, and I made sure that folder both created my test project and the ordered test list.

But still I get the same error when attempting to run the tests. Any ideas?

2
visual-studio-2010tfstfsbuildmicrosoft-test-manager
Did your build compile and output the binaries containing the tests? MTM needs to run the tests from the DLLs the build made that are saved to the build drop folder. - Ryan Riehle
No I thought it might make more sense to keep UI test projects and production code separate, so I have been building it separately. Would it be easier to add the coded UI test projects to the production build, or would it be just as easy to create a build for the UI test code? - Ciaran Gallagher

2 Answers

1
votes

Tests must be assigned/linked to builds that contain the test DLLs. Add your test projects to the solution they are testing so that they are built together.

0
votes

Select appropriate 'build in Use' which contains your test dlls. Change test plan properties for 'Build in Use' and save.