Forum Discussion
HKosova
Alumni
14 years agoHi Sudhir,
TestComplete doesn't specifically support the WebKit .NET component used for displaying charts in your tested application. As you have already figured out, a possible approach to identifying elements rendered by WebKit is to use MSAA. Another option to work with the WebKit component is to use native properties and methods of the WinFormsObject("webKitBrowser1") object in your application, in particular, the Document property. This way, for example, you should be able to access the web page's DOM elements and their attributes.
You can also vote for adding extended support for the WebKit .NET control in our survey here:
http://support.smartbear.com/products/more-info/testcomplete-survey/
As for the issue with the clicks recorded on the parent Grouping object instead of the child objects, I've reproduced it and forwarded it to our developers for analysis, as it might be a bug in the recorder. Thanks for drawing our attention to this, and sorry for the inconvenience.
In the meantime, you can manually edit the recorded test and specify the needed target object for the click, e.g. grouping.grouping.Grouping(<some number>).Edit("<Label text>"). To find out the name of the Edit object corresponding to the needed chart label, please examine the chart object hierarchy in the Object Browser.
TestComplete doesn't specifically support the WebKit .NET component used for displaying charts in your tested application. As you have already figured out, a possible approach to identifying elements rendered by WebKit is to use MSAA. Another option to work with the WebKit component is to use native properties and methods of the WinFormsObject("webKitBrowser1") object in your application, in particular, the Document property. This way, for example, you should be able to access the web page's DOM elements and their attributes.
You can also vote for adding extended support for the WebKit .NET control in our survey here:
http://support.smartbear.com/products/more-info/testcomplete-survey/
As for the issue with the clicks recorded on the parent Grouping object instead of the child objects, I've reproduced it and forwarded it to our developers for analysis, as it might be a bug in the recorder. Thanks for drawing our attention to this, and sorry for the inconvenience.
In the meantime, you can manually edit the recorded test and specify the needed target object for the click, e.g. grouping.grouping.Grouping(<some number>).Edit("<Label text>"). To find out the name of the Edit object corresponding to the needed chart label, please examine the chart object hierarchy in the Object Browser.