Hi Mario, I have not found a viable solution yet. Since I am not able to find any direct solution, I am thinking of two possible workarounds:-
1. Push the expected images onto the device before you start running your tests. You can give the path of the expected images in your code, so as to suite the path where you push your expected images. So here the complete project includes i) Pushing the uiautomator jar onto the device ii) Pushing the expected images onto the device iii) Running your uiautomator tests 2. Completely execute the test cases, without image comparison. After execution, collect all the captured images from the device and then compare them with the expected images on your system. So here the complete project includes i) Running your uiautomator jar ii)Collecting the captured images from your device iii)Compare these with the expected images on your system. All these setup can be automated. If in-case, you found a better solution during these days, please let me know. On Tuesday, April 15, 2014 12:58:33 AM UTC+5:30, Mario Rosales wrote: > > Hi! > > Actually looking the same information, were you able to find the solution? > > On Thursday, April 10, 2014 1:25:17 AM UTC-7, vedantham udish wrote: >> >> >> In UiAutomator, there is a method to capture Screenshot. But, is it >> possible to store an expected image in our project and compare the current >> captured Screenshot with the expected one inside the jar file during the >> test execution? If any one has implemented this, request you share your >> inputs. >> >> Thank you! >> > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
