Traverse a Tree in Find Object
Hi I need help to traverse to a particular object in a single find command. the name mapping does it but in case movable panels are at run time i need to put forth find parameters like this 1. Pa...
Forum Discussion
Expecting something like
find [parent prop name1 ][parent prop val 1 ], [parent prop name2 ][parent prop val 1], [final object prop nam][final object prop val]
Not sure what you are expecting. If you want to access objects in the child levels, you can use depth. If you have unique properties, then you can do by passing DEPTH.
someParent.Find(PropName1, PropVal1, Depth)
For Ex: Your object is in 3rd sub level from your parent; (You can see the hierarchy using Object Explorer)
-- 3rdParent
--- 2ndParent (1st sub level)
--- 1stParent (2nd sub level)
--- yourObject (3rd sub level)
3rdParent.Find(PropName1, PropVal1, 3)
Based on the DEPTH you are passing, FIND will search up to that level using the passed properties/values.
I am not trying to give a depth. Depth in this case is Extended find. Such extended finds in complex Dojo/Angular applications take uptoi 20 30 minutes to just find a single object with good enough name mapping of frame also.
I need to recursively select parents and thus the final child. So I am trying to give parents property names and property values in the find .
Hi,
Any real reason to have a single .Find() call?
Anything that prevents you from creating a helper function that will get some root object found by initial .Find(), do a search for the needed object considering actual state of the object like you mentioned in your initial post and return the found object?
This helper function can be used than throughout your test code and/or keyword tests.
Yes a helper function would be very helpfull, I have them. But my organization is very Sensitive[Sic]. People cant understand what it does and get confused by a little bit of strong logic. A TC official function would be very helpfull. It should be very small also. Either use existing find and recurse OR we can also justify good performance by eliminating actual manifestation of an object into variables and find objects below them create next object etc etc etc if TC can actually use their internal mechanism.
