Unable to go to page in chrome
code: Browsers.Item("chrome").Run(); Browsers.CurrentBrowser.Navigate("http://osm.org"); chrome version: Version 31.0.1650.63 m TC version: 9.31 The ...
Forum Discussion
As my signature says, I am not working for neither Google nor for SmartBear, so the text below is my wild guess based on some experience...
a) I am far not sure that Google (or FF) development is too concerned to keep the compatibility with the previous versions as for the internal implementation and access;
b) Likewise I am far not sure that they inform beforehand all those who use their browser(s) as a platform (for TestComplete Chrome is one of the platforms for web testing) and let them know what accessibility changes are going to be implemented;
c) I don't know if SmartBear has any agreement with Google, but even if they do, I think that some (bureaucratic) procedure must be followed to request how to deal with this or that internal implementation change. In the worst case, SmartBear may be left on their own to figure this out;
d) Previously, it took SmartBear reasonable time to release the patch to support updated browser.
Considering the above, I think that:
a) Patch will be available soon :) ; and
b) It is a good idea to have a controlled test environment which does not update on its own but only after your considered decision. After all - if Chrome is allowed to update itself in the test environment (say, from v31 to v32), this effectively means that you stopped testing on v31 and moved to v32. But can you guarantee that all your users will update? And if they not, are you ready to accept the risk that something that appear to work on v32 will fail miserably under v31?
Isn't the better approach not to update automatically and unpredictably but to create another test environment with the new version installed and execute tests on these two environments until you stop to support the old version of the browser?
a) I am far not sure that Google (or FF) development is too concerned to keep the compatibility with the previous versions as for the internal implementation and access;
b) Likewise I am far not sure that they inform beforehand all those who use their browser(s) as a platform (for TestComplete Chrome is one of the platforms for web testing) and let them know what accessibility changes are going to be implemented;
c) I don't know if SmartBear has any agreement with Google, but even if they do, I think that some (bureaucratic) procedure must be followed to request how to deal with this or that internal implementation change. In the worst case, SmartBear may be left on their own to figure this out;
d) Previously, it took SmartBear reasonable time to release the patch to support updated browser.
Considering the above, I think that:
a) Patch will be available soon :) ; and
b) It is a good idea to have a controlled test environment which does not update on its own but only after your considered decision. After all - if Chrome is allowed to update itself in the test environment (say, from v31 to v32), this effectively means that you stopped testing on v31 and moved to v32. But can you guarantee that all your users will update? And if they not, are you ready to accept the risk that something that appear to work on v32 will fail miserably under v31?
Isn't the better approach not to update automatically and unpredictably but to create another test environment with the new version installed and execute tests on these two environments until you stop to support the old version of the browser?