Issues working with multiple test developers in one solution
Posted: Wed Sep 02, 2015 4:43 pm
Environment: MS Server 2012r2 VM
Ranorex version: 5.3.2
TFS version: VSO 2013
Visual Studio: Premium 2013
Hi,
I have been the sole tester developing Ranorex tests. Recently however I have had a colleague join me, working on the same Ranorex project. This is causing problems with checkins. These issues result in VS Conflicts and also modules not being copied between checkins. For instance, I can check in a new module in my instance of Ranorex, but when my colleague then does a Get Latest or checks in his own work, that module doesn't always appear in his instance of Rx and causes build errors. Oddly though, we generally we find that the modules have copied across but and I can add them back into the solution on the Rx instance on his machine.
This maybe caused by the way we are doing checkins, but we have had issues doing checkins using Ranorex and also using Visual Studio. Please can someone advise the correct way of doing our checkins and sharing source control as this is becoming more problematic and will be further complicated when I have another colleague join my team in a couple of weeks.
Cheers,
James
Ranorex version: 5.3.2
TFS version: VSO 2013
Visual Studio: Premium 2013
Hi,
I have been the sole tester developing Ranorex tests. Recently however I have had a colleague join me, working on the same Ranorex project. This is causing problems with checkins. These issues result in VS Conflicts and also modules not being copied between checkins. For instance, I can check in a new module in my instance of Ranorex, but when my colleague then does a Get Latest or checks in his own work, that module doesn't always appear in his instance of Rx and causes build errors. Oddly though, we generally we find that the modules have copied across but and I can add them back into the solution on the Rx instance on his machine.
This maybe caused by the way we are doing checkins, but we have had issues doing checkins using Ranorex and also using Visual Studio. Please can someone advise the correct way of doing our checkins and sharing source control as this is becoming more problematic and will be further complicated when I have another colleague join my team in a couple of weeks.
Cheers,
James