To Niranjan:
Inclusion of PatchServices.jar module into your Android tested application as per Tanya's reply is required to make it open for TestComplete. When the application is open, you can create tests that operate with application's UI objects, but not their images, thus making your tests way more reliable and powerful.
The bad news are that even open mobile applications do not provide TestComplete with the information about web page displayed in the WebView control. Currently TestComplete supports testing of mobile web applications that are executed on the desktop via Chrome browser in the mobile client emulation mode (
http://support.smartbear.com/viewarticle/57398/).
For the hybrid mobile applications I see only one possible approach so far:
-- Use TestComplete to drive your tested mobile application to the point when it requests data to be displayed in the WebView control;
-- Get the request string been sent to the web server from mobile application (you may ask developers to provide you with this possibility);
-- Launch Chrome in Mobile Browser emulation mode and navigate to the address obtained on the previous step;
-- Continue with the web page test on the desktop;
-- Get the required data from the web page, switch back to the mobile application and feed it with the obtained data.
Hope, this approach will work for you.
Also I will appreciate if somebody share their experience with testing hybrid mobile appication(s) using TestComplete.
To Simon:
I probably missed something in your question, but image-based testing, along with OCR functionality exists in TestComplete for a long time:
http://support.smartbear.com/viewarticle/57039/http://support.smartbear.com/viewarticle/55011/