You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In previous discussion of condition handling it was mentioned that currently condition checking does not allow timeouts to be set.
It would be great to have this feature. So we can do:
'element.is(displayed, new TimeoutSeconds(0));'
It would be nicer to do this in a more fluent way e.g:
'element.is( displayed, within(5).seconds ); // -> boolean '
or
'element.is( displayed, currently ); // -> boolean, i.e. No waiting'
Happy to help implement this if you feel it is a good idea.
The text was updated successfully, but these errors were encountered:
@davebassan any comment on this? It would be better to be more fluent about negative conditions and zero timeouts. Either way we need to get some closure on this.
@MikeAScott have you had a go at implementing this?
In previous discussion of condition handling it was mentioned that currently condition checking does not allow timeouts to be set.
'element.is(displayed, new TimeoutSeconds(0));'
'element.is( displayed, within(5).seconds ); // -> boolean '
or
'element.is( displayed, currently ); // -> boolean, i.e. No waiting'
Happy to help implement this if you feel it is a good idea.
The text was updated successfully, but these errors were encountered: