Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
bring back automatic retry for all Find methods
See original GitHub issueI would like to pick up the discussion started here again.
To me it seems very common that UI elements need to build up before the can be found using the AutomationElement.FindXXX(...) methods. If you have fairly a dynamic (and slow) UI, this can happen a lot and forces you to use Retry all over the place when finding the elements.
So I suggest that you can optionally enable and configure the retry behavior for all AutomationElement.FindXXX(...) methods in a block of code or in a test method.
This way we do not need to clutter our test code with a lot of Retrys.
Something like this did already exist in FlaUI 1.3 to some extend.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@atresnjo I would have to mirror all the existing
FindXXXmethods as extension methods and add those parameters. I feel that they should be in FlaUI out of the box.I’ve actually added the Retry.Find methods. Feel free to check them out.