Champion Level 3I disagree. Comparing the fonts and such to see if they rendered properly on a particular screen is still what a manual test would do if you didn't have automation.
In any case, I think the pictures will still work for you. You take a baseline picture for ScreenSize1 with Language1 and save that. Use that in a checkpoint in your test to compare with what's actually on the phone. If anything doesn't match, then the test will fail. If you want more specific results, then take pictures of each field separately and do the checkpoints that way.
That approach will require to generate hundreds or thousands of baseline pictures.
It would be good if the tool can grab the text displayed in the UI as it is and compared with the approved source target text.
This will simplify the process and easier to automate (cheaper since faster - no need to manually generate and verify thousands baseline pictures).
I hope TestComplete can accommodate this needs in the near future.
Champion Level 3Okay, how about giving us an example of how this would work. I'm interested to see how you would have "approved source target text" without setting up baselines.
Sorry for the delay in replying Marsha
As an example, let say you have a receipt from a store. That receipt has some pictures/logos, numbers and texts.
That same receipt has to be translated into 40 different languages.
You have the approved target translated word by word source. All you need to do is to check if there is any clipping, truncation, hyphenation and also checking whether the translated text does match with your approved translated word by word source.
We need to do this for all languages, in my example 40.
The receipt itself might slightly change during any period due to customisation but the text contents are still the same. Perhaps just moving positions, etc. Therefore it would be a daunting task if every time you have any minor change or any re-organisation of text then you have to generate baseline library images for 40 languages.
It would be good if TestComplete can nominate an area in the picture and detect any text displays there and we can get the actual text displayed in the UI for comparing it against target source.
I'm not familiar with mobile testing but, if the interface between TC and your mobile app is similar, the way I'd do it in a desktop or web application is look for the property that contains the text in the object in the application.
Say, for example, in a web application I have a textbox that contains the receipt text. That textbox would have a property called Text or wText or contentText which would contain the plain-text version of what I see on screen (no fonts, formatting, etc). I'd build a baseline of a simple text file (Stores -> Files) for each language baseline and then do a check of that property to the contents of the associated text file and look for differences.
