Thursday, August 02, 2012 7:06 PM
So I have asked in both the TFS forum as well as the testing group about configurations for TFS with test manager but both groups are getting confused, so I wanted to lay it out again in more detail so myself and others can get a detailed explanation on the process.
I have TFS, test manager and visual studio installed on one virtual computer where I want to run automated tests from. So far I have been able to record and create those coded UI tests in test manager into Visual studio 2010 and they have been able to run successfully. The part I need help with IN DETAIL if you know is how to configure TFS and the build definition to find the test controller so that when I go into test manager and I want to run those automated tests they will be able to run. Here is what I have done so far:
1. Create coded UI tests
2. Associate those tests to the test cases in test manager
3. Assign builds and build definitions for those test cases in test manager
4. Create test settings and assign the test controller to the test agent and those to TFS. Also created a PHYSICAL environment to run the tests. These tests will only be run on this virtual computer where EVERYTHING is installed so it only needs to find things on its own drive.
5. When I try to run those automated tests test manager says there was an error and that it cannot find the build directoy.
So can someone really lay out the basic steps on how the builds should display in TFS as well as how to create the build definition to be able to work with my automated tests in the physical environment I created in test manager. (if you had screenshots that would be great!)
Also if you could explain how to fix the error about the build directory not being found that would help, and what exactly needs to be in the build directory for test manager to run. .
Please let me know if you guys have any questions, I have been working on this for awhile and I have been searching through every msdn page microsoft offers about test manager and TFS but none really lay it out like I need to or describe my problem in detail enough for me to solve it.
Thanks guys! :)
- Moved by John QiaoMicrosoft Contingent Staff Friday, August 03, 2012 8:52 AM (From:Team Foundation Server - Setup)
Friday, August 03, 2012 9:00 AMModerator
Thank you for your post.
For "Build directory of the test run is not specified or does not exist", the possible causes are:
1. The account under which test controller is running does not have read permission on the build directory. (The build directory is same as the build drop location of build associated with this test run.)
2. The build directory corresponding to the build associated with the test plan does not exist. By default, only last 10 successful builds are archived. So, if an older build is associated with the test plan, it is likely to have been deleted.
Resolution: Make sure the build directory exists and the test controller service account has read permission on it.
If the build is deleted, then go to the test plan properties (using Microsoft Test and Lab Manager) and update the build number associated with it.
Lily Wu [MSFT]
MSDN Community Support | Feedback to us
Friday, August 03, 2012 12:07 PM
Thank you for your input,
I did give my test controller (the lab computer) access to the build folder and it does exist. What exactly needs to be in the build folder though? Maybe that is where I am going wrong.
Friday, August 03, 2012 2:16 PM
I have been getting the same error.
I have been attempting to run the tests on the latest gated checkin build, which outputs to a folder on the C drive on the test controller. I checked this folder - it has read rights to the test controller user and it also appears to contain all the build files - including the test project and ordered test list that I actually want to run.
I can't think of any reason why MTM is not finding the build directory. It does not make any sense. I already examined the build definition to make sure that the build was outputting to the correct location.
Any other ideas?