-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to find reported element when there is no accessibility Id in GTXiLib report? #15
Comments
@selin194 you have frame of element which might help you. |
I see, maybe I can use address information too. (By stopping my test at a specific point and see the address of the each element and check failure). Is there a way to add accessibility Id to the elements to the report? @sishuiOS , thank you. |
I realize this isn't a perfect solution, but the failing element is set in the NSError's userInfo which is logged by the check: GTXiLib/Classes/NSError+GTXAdditions.m Line 62 in 61eb982
If you put a breakpoint in this file, you can log whatever you'd like about the element in question. I do agree that the element's description should include some additional info:
@j-sid I don't think it should be too difficult to add some extra logging to the element's description in |
We can add additional key-value pairs to the |
@selin194 we certainly could, but the In the meantime, though, you could try adding a breakpoint to that file to do the check yourself. |
@selin194 Hi ..I have integrated |
Hey @sishuiOS, for UITests we need to use EarlGrey library and create a new target by selecting IOS Unit Testing Bundle. After that we need to create a scheme whose target is newly created one. After that we can start to use GTXiLib features! Let me now if you have any question! |
Hi all,
I have a question. I have successfully called GTXiLib on my UI tests and get a report of accessibility checks. However, I receive error report like:
I can not understand which UI buttons does this report try to point on. How can I learn which button is failing by reading this report? I mean should not this report include accessibility Id on the report to know the button that fails? Thank you @niksawtschuk @j-sid !
The text was updated successfully, but these errors were encountered: