Process for running test automation against Chrome Beta
briley last edited by
I've been tasked with determining and implementing a method to run (not yet created) automated tests against the beta version of Chrome (https://www.google.com/chrome/beta/).
We have yet to decide on tooling and scheduling, but even with something in place, I am trying to understand how the process can be automated entirely. Has anyone set something like this up successfully or have recommendations?
Demir last edited by
It means you can ask for the specific beta target version (currently 75) from your dependency management system and indicate the location of your Chrome Beta.