Dependency Updates on Automation Projects

What restrictions or blockers do you face when trying to keep dependency versions updated for your automation project?

E.g. keeping Selenium, Maven, your drivers etc up to date.

The main issue I faced when trying to keep test suites’ packages up to date is that sometimes different versions of different packages weren’t playing nicely together or requiring another node version (we test in node.js environment). So whenever we plan to update versions, it’s always a must to rerun the whole test suite to ensure everything still works as expected:-)

1 Like