Open timmikk opened 8 years ago
Thanks for opening the issue. I've a slightly different solution in mind. How about using Settings
to declare a timeout? Would that help you, too?
Could you provide a basic code snippet where this would help you? I would like to have an approach that e.g. WindowFinder uses: .withTimeout(10000)
..
No feedback :-/
Currently the BasicComponentFinder fails immediately if no match is found. In many situations it would help that it tired to find for specified time before failing. This would make tests more robust.