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
Has been an ongoing issue forever. About the only thing people will tell you on this forum is to disable updates which in my opinion is completely unacceptable for many reasons.
One... our system administrator would likely have a melt down if he knew we had any PC running with an out dated browser.
Two...our customers do not disable browser updates. We are mandated to configure our systems to the most commonly used configuration by our customers to increase our likelihood of catching issues that would affect a majority of our customer base.
I sent a request to our network team to find out how they suggest I do this. I agree, I don't want to completely turn off updates for an extended timeframe. I simply want to make sure there is a patch for TestComplete/TestExecute before the update gets applied.
I don't think you're going ot get pathces from SmartBear before Chrome updates the browser unless SmartBear is on some kindo fo list that gets advanced notices on any changes in the browser from Chrome. While I don't mind a few days for a fix to come, it is problematic when it's more than a few days.
I realize that. I am not expecting SmartBear to have the patches before the update comes out. I am just looking for a better way to manange WHEN Chrome updates so I can delay the update until a patch is available.
