I've found a few threads that are related to my question but none of them seem to be exactly what I am facing. Apologies if this is a duplicate.
In my example I have changed the directories to ones that are easier to follow though are representative of the situation I am in. (The actual project directories go fairly deep and I think will just confuse the issue).
The problem that I have is that when I first started on a project of automating UI cases not much had been done in terms of integrating with TFS. I had locally mapped the project to my machine and was working with this integration. After some discussions with other QA in the company we settled on a common layout for how to map projects. In Visual Studio I then remapped the project from:
d:\different\local\path\to\project
to this:
d:\local\path\to\project
For awhile things were fine. However, we have now upgraded to Test Studio 2013 and the mapping is not quite working. When I open the project I get this message:
The TFS Local path does not match the actual project path!
I also get this message in a dialog:
Remote path $/Path/To/Test/Project does not map to a parent of local path d:\local\path\to\test\project
When I try to reconnect to the TFS server and pick the project it has the local path as:
d:\different\local\path\to\project
This is the older location which is no longer correct. What steps do I need to take to get Test Studio to stop looking in d:\different\local\path\to\project and start using the correct directory?
I haven't been able to find it in a config file or in the registry. I also tried re-installing in the hope that that would clear out settings.
Thanks!
4 Answers, 1 is accepted
When you use Test Studio to connect a project to TFS, it creates a new TFS workspace in the form [user]_[macnine]_WebUITestStudio. This workspace is controlled and maintained within TFS. It's this workspace that manages the mapping from the TFS folder to your local HDD.
If you would like to start from scratch (which is probably a good idea in your case) I suggest you use Visual Studio's source control explorer to delete this workspace and let Test Studio recreate it for you. Here's a short video showing how to locate and delete the xxxxx_WebUITestStudio workspace:
http://screencast.com/t/BGBQBY5Rxfd
Cody
Telerik
Rank 1
I had found this in Visual Studio but got busy and didn't remember to update this thread. I appreciate the info.
In my experience this became much more of an issue with the upgrade to the latest 2013. I am curious if this is expected although since the issue is resolved it is not a pressing point.
Regards,
Kevin
...this became much more of an issue with the upgrade to the latest 2013.
I cannot explain why. We did not change our TFS integration at all between 2012.2 and 2013.1 releases of Test Studio.
I am curious if this is expected although since the issue is resolved it is not a pressing point.
It's not crystal clear which behavior you're referring to here. We have always created a workspace by the name [user]_[macnine]_WebUITestStudio ever since we added TFS source control integration into Test Studio.
Cody
Telerik
Rank 1
I understand that the workspace has always been used. I was just curious why with the 2012 release I could open the project (regardless of workspaces) by browsing to it. Check-ins and check-outs etc all seemd to work all right.
But, with 2013 this no longer worked.
As I said, though, since the issue has been resolved this is not a pressing point.
Best Regards,
Kevin