-
-
Notifications
You must be signed in to change notification settings - Fork 513
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
Better ways to override implicit timeouts for Screenplay Targets? #558
Comments
You can use the WebElementStateMatchers.isCurrentlyVisible() matcher, e.g.
|
Hmm, I don't actually want to use it in an assertion, but more to make a task conditionational e.g. how would I re-implement
|
Also, I want to immediately determine the count of items in a question where sometimes the number may be 0:
But when the locator is not present a delay is incurred equal to |
There are times when I want to immediately work out whether a screenplay target is visible or not, but not wait until my implicit timeouts have completed. Historically (pre-Serenity) I did this most effectively by doing a findAll() with a 0 second wait condition. So to emulate this in Screenplay/Serenity, I've created a helper method as follows:
This seems like a hack. Is there a better way please?
The text was updated successfully, but these errors were encountered: