Forum Discussion
Why do you need the visual image screenshot of actual vs. expected for instances where the test passes? If it passes, that means everything is there... Actual = Expected. If it fails, as with an error, then the onlogerror screenshot will show you the Actual and the test log, in the information in the log, will detail what doesn't match.
For that matter, an image comparison of actual vs expected is moot for object checkpoints. An object checkpoint takes a snapshot of the object and your selected properties and compares that snapshot to what's actually rendered in your application. If you pick your properties within the checkpoint properly, screenshots don't matter. If you truly want an actual vs. expected image, then your best bet is to use region checkpoints/image comparison.
Hi shahid,
I don't really understand what exactly you want to achieve.
Let's say the objects are different. You can take the image of the actual object from the screen, but where do you think the expected image will come from (taking into account that you don't want to use Regions and therefore Image comparison)? It is impossible to have EXPECTED images of the object, on the one hand. On the other hand, it is impossible to have screenshots of objects for ALL checkpoints, because some of them simply can't be captured (e.g. file checkpoints, database checkpoints, etc.).
Another example: the objects are equal. What do you expect to see in the log? Two similar pictures? An empty picture, which will guarantee that objects are equal? A picture which will display both expected and equal images?
In general, can you explain, what is your your task and what exactly you want to see in the log?
Related Content
Recent Discussions
- 19 hours agojstaehlin
- 2 days agoAivanitskiy