-
Notifications
You must be signed in to change notification settings - Fork 12
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
Keyword "Find All Elements" fails (here: Property "ClassName" is "Not Supported") #160
Comments
@JanR-W This was not considered within the method that properties are not available.
Since these are accessed in the Find_All_Elements method and should be saved as a list, there is probably an exception within the execution on this element. This is a bug that we will fix. We could solve this with an argument that can be selected and also that there is simply an empty string. |
That was a very quick fix, thank you so much! EDIT: I can also confirm that |
Hello,
in our AUT the UI elements have the property "ClassName" show up as "Not Supported":
Apparently this leads to an error when using the keyword
Find All Elements
(I'm using the rfdebugger library to debug my keywords interactively inside of my console, but the same error occurs if I use the keyword inside of my test scripts):Would it be possible to extend
Find All Elements
with an (optional) argument so that it only tries to read the property of the found elements I actually need and know is supported in my AUT? If not specified it could keep its old behaviour to return all three properties (making it hopefully a non-breaking change to the keyword).To make it hopefully a bit more clear: I'm thinking of something like this:
None
, if not specified>The text was updated successfully, but these errors were encountered: