Forum Discussion
This is one reason why, for most situations, I don't depend upon image comparisons for doing my tests. Different resolutions, color saturations, etc., make for all sorts of mess when doing those comparisons.
If all you're concerned with is the text content of the component, I would look at using a property checkpoint or similar comparison on the component's text, contentText, wText, Caption, or some similar property, depending upon the component. This will validate the text without needing to involve anything like color tolerance.
- sameerjade8 years agoFrequent Contributor
Thanks, Robert for the reply. I did try using the property checkpoint ('check object content or properties' > 'compare a collection of object properties' since I want to test several buttons, text boxes, header text etc). It creates an object and gives me a script line which I put inside my script. When I run the test, this check passes but I don't really know what exactly it tested. For eg, in image comparison, we can see the actual and expected images. So, I tried to change the baseline object by changing a numerical text value in the window to be tested, created a new property checkpoint which gave me a new script line. Now, when I run the test, I expected it to fail since I changed my baseline to a new one but my actual is the same because of the test steps are still the same. However, the test still passed. Now, I am suspicious what the property checkpoint it really testing. Does it only test things like, window height, width etc?
Thank you!