Managing multiple repositories

Best practices, code snippets for common functionality, examples, and guidelines.
HansSchl
Posts: 125
Joined: Wed Sep 19, 2018 10:05 am

Managing multiple repositories

Post by HansSchl » Mon Mar 07, 2022 9:16 am

Dear all,

of course I read the help page in this topic at https://www.ranorex.com/help/latest/ran ... ositories/.

My test suite is rather complex and contains dozens of tests, and we were four people who developed tests. That is why I created several repositories. Currently there are 35 repo files, and I think this is now going too far. Test developers are not always as disciplined as one would wish, and so items were created in the "wrong" repo, and we have lots of duplicate items, spread across those 35 repos, which, of course, they were not given identical names - while one called a field "name_input", the other would keep a default name like "text4733". It took me weeks to carefully rearrange and rename repo items, making sure that every single test is still running after each iteration.

My question is, what is your experience with this issue? Do you clean up repositories now and then? Do you keep lots of small repos, or do you prefer to have just one, but a huge one? Any advice how I should handle this in the future?

Best regards
Hans

User avatar
odklizec
Ranorex Guru
Ranorex Guru
Posts: 7465
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: Managing multiple repositories

Post by odklizec » Mon Mar 07, 2022 11:35 am

Hi,

I'm afraid, there is no good solution to this problem. This is exactly why I'm using only one repository per project. Of course, there are sometimes merging problems and changes from multiple users often needs to be merged manually. But single repository helps with enforcing the same naming convention and xpaths construction. Multiple repositories are a nightmare to keep and maintain.
Pavel Kudrys
Ranorex explorer at Descartes Systems

Please add these details to your questions:
  • Ranorex Snapshot. Learn how to create one >here<
  • Ranorex xPath of problematic element(s)
  • Ranorex version
  • OS version
  • HW configuration