My organization is starting up an automation team, and we are still working on our structures and procedures.
We are using Git to store automation code, and we seem to be of two minds; some feel we should put all our automation code in one repo, and others feel we should separate code into multiple repos.
Here's the wrinkles: Much of the automation we will write is not for AUTs. It is for mission-critical third-party software, the actions of which may induce certain internally designed processes to do certain things. Most of these are integration layers between diverse third party applications. The overall software ecosystem is very large with diverse and mostly third-party applications. As a result, there won't be hardly any shared code between the frameworks for each application.
So far the best argument for single-repository design is that we can run all tests at once from one repo. There is no scenario, though, where we would run all tests at once.
I am proposing separate repos for each application we will automate, with an additional "common" repository for whatever few things we can share.
Also, there will be 6 automation developers, most of the time each will be the only one working on a particular application, for the small ones; but for the larger applications, there will likely be two or more working on it.
Do you agree with my camp of having separate repos? Can you give me pros and cons?