Sometimes automation projects either fail or are made far more difficult because developers don't adopt automated testability as a design requirement. Are your developers aware of these?
Lack of automated testability requirements was one of the biggest challenges I faced as an automation architect. Object names changing caused countless hours of script rework and additional expense. We tried on numerous occasions to help the development organizations understand the impact to projects caused by "refactoring".
I think having formal automated testability requirements that we could create defects against would have gone a long way towards a solution!
Lack of automated testability requirements was one of the biggest challenges I faced as an automation architect. Object names changing caused countless hours of script rework and additional expense. We tried on numerous occasions to help the development organizations understand the impact to projects caused by "refactoring".
I think having formal automated testability requirements that we could create defects against would have gone a long way towards a solution!