Chrome, Opera support
Does AQA have plans to add a support of Chrome and Opera browsers to TestComplete? If it does when will this happen? Thanks in advance.
Forum Discussion
AlexKaras
Champion Level 1
Champion Level 1Hi Alexander,
> - TC doesn't support some popular browsers
> - We need to test under the browsers which are not supported by TC
The above is evident. But according to my understanding, substitution of the rendering engine does not mean that TestComplete begins to support unsupported browsers. From my point of view, in this case TestComplete just gets a possibility to access tested web page elements and control these elements via rendering engine. I guess (and I hope that Automated's Support will correct me if my guess is wrong) that, for example, with IE, TestComplete does not interact with IE itself, but interacts with its rendering engine. So, when, for example, Chrome uses IE's rendering engine and TestComplete is used to control this combination, this means that TestComplete still works with the same IE engine. The only difference is that rendered content is displayed not in IE, but in Chrome. The disadvantage of this approach is that it is not possible to say anything as for how the given page will be rendered and displayed in Chrome using its native renderer. Also, if something is shown incorrectly, it is not possible to say if the problem was caused by the IE renderer or how Chrome displays data provided by non-native renderer.
Considering the above, I still don't see the reason to substitute the rendering engine in unsupported browsers. (Unless there is explisit task to check how the data provided by the non-native renderers are displayed by this or that browser.)
> - TC doesn't support some popular browsers
> - We need to test under the browsers which are not supported by TC
The above is evident. But according to my understanding, substitution of the rendering engine does not mean that TestComplete begins to support unsupported browsers. From my point of view, in this case TestComplete just gets a possibility to access tested web page elements and control these elements via rendering engine. I guess (and I hope that Automated's Support will correct me if my guess is wrong) that, for example, with IE, TestComplete does not interact with IE itself, but interacts with its rendering engine. So, when, for example, Chrome uses IE's rendering engine and TestComplete is used to control this combination, this means that TestComplete still works with the same IE engine. The only difference is that rendered content is displayed not in IE, but in Chrome. The disadvantage of this approach is that it is not possible to say anything as for how the given page will be rendered and displayed in Chrome using its native renderer. Also, if something is shown incorrectly, it is not possible to say if the problem was caused by the IE renderer or how Chrome displays data provided by non-native renderer.
Considering the above, I still don't see the reason to substitute the rendering engine in unsupported browsers. (Unless there is explisit task to check how the data provided by the non-native renderers are displayed by this or that browser.)