Hi Pavel,
unfortunately I cannot upload the snapshot (it's too complex) but I am attaching a screenshot of the part in question.
2022-04-14_10h10_19.png
The problem is that those UI elements (containers, buttons, and texts) have no proper automation ID. The text controls are next to the respective button controls, so users would perceive the buttons as labels to the text controls. I don't like this GUI design, but it is what it is.
The test must access the text control next to the button with a specific label. I cannot say in which container this control will be found, so my idea was to find the button with .../container/button[@text=$ButtonName] and then go to the next sibling, which is the text control: .../following-sibling::text. The test reads the $ButtonName from a data source, and tests all those button-text control pairs in a loop.
This works most of the time but sometimes fails, and when it fails, I get a somewhat strange timeout error in the report (see
https://www.ranorex.info/invocation-did ... 21450.html), so I was wondering whether following-sibling might cause the problem. By the way, with "sometimes" I mean in a low percentage of all test executions. There is no specific test sequence which fails reliably, it just happens now and then.
Regards
Hans
You do not have the required permissions to view the files attached to this post.