Hi, can't you improve the display of image captured on failure?
In the screenshot, as you can see, one cannot clearly distinguish texts or any other small component.
Isn't it better to enlarge image when window size is maximized or can't you add a zoom functionality?
3 Answers, 1 is accepted
Hello Nick,
Thank you for sharing your thoughts on Test Studio features for troubleshooting a failing test.
Though, the idea of this image on failure is to point you if the test run did get to the page you expect, but not to identify the errors through the image. The res of the step failure details are designed to help you resolve the failure.
If you are still not sure what is causing the misbehavior, you can enable the annotations - these will highlight the target element of each step. Then, observing the test execution will help you understand what might have gone wrong.
If the suggested tools are not helping you to sort out the failing test, please, do not hesitate to elaborate more on the encountered issue - I will be happy to assist you further. It will be helpful if you share the complete failure details - these can be exported from the Failure tab through the respective button.
I hope that this information will be of further help for you. And, I remain available to continue the discusison in case you have any further questions or doubts.
Thank you for your understanding in advance.
Regards,
Elena
Progress Telerik
Rank 1
Iron
Thank you for your answer @Elena,
But to correctly check if we have reached the desired web page (as you said), we should have a clear image.
You can confirm that two different web pages can be, at first glance similar but after looking more closely we can notice some differences (text values, colours...).
What is the use of these blank (white) space around the failure image (I've attached in my previous post)?
You could just size the image as the window is resized : that would be a good start.
Hello Nick,
Thank you for sharing your ideas on the Failure details.
Actually, in the Image tab next to the image on failure, there could be an expected image, which additionally can help you in identifying what causes the test failure. I suspect that these failure from the shared screenshot is from a remote test execution and this why the expected image may not be available.
In addition to the images from these details. you can explore the DOM tree on failure, which can be helpful for identifying any text values, etc. Depending on the type of error, the Resolve Failure tab may suggest the proper solution out of the box.
Please, let me know if there is any test failure, which bothers you and if I can help you with this in particular?
I mentioned this option in my previous reply, however, will refer this again - sometimes the actions during test execution are being sent really quick one after the other. This may lead to unexpected behavior of the application during the run and may be difficult to identify where the troubles start actually. In such cases we always recommend the annotated quick test execution - once enabled the annotations will slow down the execution a bit and will highlight the target element for each step in the test. Observing such run, you it will be easier to sort out which of the actions are causing the inconsistent behavior.
In case the failures are not consistent and the tests are failing on different step by each execution, most probably you need to insert additional wait steps or execution delays - this is the mechanism to sync the test run with the application responsiveness speed.
Back on the topic with images, in our latest official release 2020.2.804 we introduced image comparison and OCR (Optical Character Recognition) verification. These may be of further help for the automation project you work on.
Please, do not hesitate to share further details on any failure you encounter and cannot resolve consistently - I will be happy to assist you with any issues you may encounter.
Thank you for your cooperation in advance.
Regards,
Elena
Progress Telerik