Amazing work with Test Automation University. Huge thanks again your way.
Quick question. We have a Java Selenium automation framework that was built years back back and it has never been code reviewed by any developers. Seems everyone thats worked on it has done something different interms of how they’ve structured their code. So
1 - What would you say is the best approach to refactoring it? I don’t believe are team have great automation testers, our manager knows Java from a Computer science background. Not much involvement from someone with a developer background with our framework. How would you work with legacy framework?
2 - We have one testing repository where all the automation code for the majority of our projects go. Each project is different. One issue we have is people change things eg upgrades versions or shared utilities that works for their project but breaks for other projects. We were initially thinking of having a core repo for shared code and seperate repo for the different projects. How would you tackle this? What are you thoughts around this problem?