Considering I have an existing test automation framework for a product and the plan is to do a product rewrite but seperate it into multiple components, each living within their own git repositories, what is the best approach in order to have code reuse across component repositories for test automation purposes?
As it stands, Product X we shall call it, is a giant monolith with test code inside a singular product repository with the application source. The plan is to break it into ~5 components, in 5 seperate repositories.
How do I manage a test framework here, where each component needs it's own GUI functional tests and a framework to run those?
I am very new to packaging up code to share around, but here is my understanding:
- Host an internal server for dependencies, something like Artifactory?
- Create dependencies out of reusable code, things like base page object classes, configurations, helpers etc
- Include these dependencies inside each test project in each repository
Is that a sensible approach? What should or could I do differently to make management of this as simple as possible?
