Merging tests from two different test that include coded steps from two different test projects is not officially supported. It can be done but you must take additional steps beyond just copying the files from one project into another.
The problem is the Namespace declaration that is placed at the beginning of code behind file. Here's an example of the top few lines of a typical .cs code behind file:
Test Studio will set the namespace to be the same as the name of the test project. As a result, all the Pages.xxxxx references are expecting the Pages.g.cs to be placed into this namespace. Since the Pages.g.cs file is automatically generated by Test Studio it will always be given a namespace declaration for the current test project. This is where the conflict occurs. Your Pages.g.cs file will have namespace TestProject2 while your imported code behind file will have namespace TestProject1. As a result it cannot find the objects declared in Pages.g.cs having a different namespace declaration.
If you update the namespace declaration of your imported .cs files it should fix the compile problems you are running into when you attempt to merge tests from multiple test projects into one test project.
You would actually be better off by following these steps:
1) Create new test project on computer A
2) Check in the test project into TFS
3) Computer B gets the latest to get the new test project out of TFS
4) Now both computer A and computer B can work in the same test project at the same time. The only caveat is each developer must not work on the same single test at the same time (it is not possible to merge changes made by two developers on the same single test). It's perfectly OK to work on different tests within the same test project at the same time
All the best,
the Telerik team
Check out Telerik Trainer
, the state of the art learning tool for Telerik products.