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 get it, but you're really going to have 42 PCs with an outdated browser?
Or did I misunderstand this? "update 42 PCs"
"Firefox and IE is good enough."
This is ultimately what our team decided...to stick with just IE for automated testing until this process is improved upon by SmartBear. Ultimately the decision was made when we reevaluated the purpose of automated testing (good to to do every now and then for sanity sake) and it was determined that the ultimate goal is to catch major issues with a release. Testing every browser and every scenario was not determined to be a focal point of automation since we have manual testers running those browsers. So far, for us, this has proven to be time better spent and we're able to dedicate more time to automated script expansion.
You said:
This is ultimately what our team decided...to stick with just IE for automated testing until this process is improved upon by SmartBear. Ultimately the decision was made when we reevaluated the purpose of automated testing (good to to do every now and then for sanity sake) and it was determined that the ultimate goal is to catch major issues with a release. Testing every browser and every scenario was not determined to be a focal point of automation since we have manual testers running those browsers. So far, for us, this has proven to be time better spent and we're able to dedicate more time to automated script
Fair point and this might be what we are ultimately stuck doing. We don't test everything on all browsers but we do have certain types of regression testing that we want to run on each release and on each currently supported major browser.
-" we do have certain types of regression testing that we want to run on each release"
Understood.
For us it was a nice idea to run on every browser, and sounded good to management, but we could not justify the logic behind it.