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
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.
This is software development 101.
The entire point of these beta/preview versions is for situations exactly like this where developers and testers alike need to develop for the updates prior to them being released.
Chrome releases beta versions specifically for developers prior to pushing browser updates.
https://www.google.com/chrome/browser/beta.html
In fact I can't think of any software that does not release beta or prelease versions.
For example...Windows 10 has a preview version for developers under their "insider" program.
