Managing Chrome Updates is a nightmare?
It appears that managing updates to Google Chrome is a complete nightmare when working with TestComplete. I am curious how others manage this. This week Google pushed out Chrome 42 and all my PCs...
Forum Discussion
Agree with Ryan. This is rudamentary stuff. I dont work with the Chrome plugin but I would hope that the Test Complete developers test on the Beta version and have patches ready to roll out the day the changes go into Chrome. I worked with a web based product for a couple of years that only had support for Chrome and that development team always had time to prepare before a breaking change went into Chrome. Also, as QA we tested on Beta to be ready for any changes.
"cannot find an offline version of Chrome 41"
This is what makes Chrome even more annoying. Stopping the **bleep** thing auto-updating is annoying enough. And it usually finds a way, no matter what you do.
And then, to make matters worse, finding an installer for an older version is nigh on impossible. FileHippo used to have them, but not any more.
Personally, I simply keep a copy of the offline installer of a current working version of Chrome. If things get out of sync, I just uninstall Chrome, re-install, and then do all the usual stuff with trying to stop it updating. (Still have to try Alex's folder renaming method!) So at least I have a way to go backwards rather than simply being stuck with broken software. This usually keeps me going until patches arrive.
That said, I only maintain my own PC and a couple of VM's. I wouldn't want to have to back-install 42 PC's either.
Why they can't just have an option to allow you to choose when updates are installed (you know, like every other piece of software on the planet) is beyond me .....