What's the best practice to develop a Ranorex project when working in a team? We use Perforce as our source control and it's not integrated into Ranorex.
We are starting a new Ranorex project to automate our mobile app. Previously, one person would own the project. He/she will develop all the repository items, recordings and test cases. On this new project, we want to work as a team. We are planning on splitting up our test plan and each person will develop their own repository items, recordings and test cases based on their section of the test plan. That means people will be checking in their changes while I am still developing my tests.
Our test suite has two projects in it. The first project holds all the test cases. The second project is a library project that contains all the repo items and recordings.
Here's a sample scenario:
Two people are working on the project. Both of them have pulled the latest changes.
Both people do the following:
- Develops a new test case
- Adds several new recordings
- Adds several new items to the Repository
- Modifies an existing recording
- Modifies an existing item in the Repository
Now Person B is ready to check in their changes, but before doing so they must merge in the changes from Person A. The new recordings are a no brainers. They are new and don't have conflicts. How about the others?
How do we properly merge all the Ranorex project files? I'm sure there are internal IDs the identify all the test cases and repo items. Will this cause an issue?
Thanks in advance for the help.