Skip to content
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

Waiting verification functionality #319

Closed
YevgeniyShunevych opened this issue Oct 14, 2019 · 0 comments
Closed

Waiting verification functionality #319

YevgeniyShunevych opened this issue Oct 14, 2019 · 0 comments
Assignees
Labels
Milestone

Comments

@YevgeniyShunevych
Copy link
Member

@YevgeniyShunevych YevgeniyShunevych commented Oct 14, 2019

The new functionality is here to provide fluent waitings.

Usage

The usage is similar to Atata's Should assertions. Just use WaitTo instead of Should:

Component.WaitTo.Equal("...")
Component.WaitTo.BeVisible()
Component.WaitTo.BeEnabled()

If a condition is not met during the waiting time, which is taken from AtataContext by default (AtataContext.Current.WaitingTimeout and AtataContext.Current.WaitingRetryInterval), then TimeoutException is thrown.

Implementation

WaitingVerificationStrategy

WaitingVerificationStrategy is a core part of waiting verification functionality. Its ReportFailure method throws TimeoutException.

Add WaitTo properties

WaitTo property should be added to all classes that have Should property.

@YevgeniyShunevych YevgeniyShunevych added this to the 1.4.0 milestone Oct 14, 2019
@YevgeniyShunevych YevgeniyShunevych self-assigned this Oct 14, 2019
YevgeniyShunevych added a commit that referenced this issue Oct 14, 2019
…ification strategies; Add tests: WaitTo_NoFailure, WaitTo_NoFailure_WithRetry and WaitTo_OneFailure
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
You can’t perform that action at this time.