Skip to main content

Wait action

The wait action allows you to introduce deliberate delays in your test execution:

  • Wait for time-based operations to complete
  • Simulate real-world delays between user actions

As a developer you can use this action as a temporary workaround during debugging complex scenarios.

In widget tests, the wait action is instant - it doesn't actually consume real time. The framework fast-forwards through the specified duration immediately, allowing schedulers, timers and animations to complete without slowing down test execution.

In integration tests, the wait action actually waits for the specified duration in real time. This affects test execution time and should be used justifiably.

Parameters​

ParameterTypeDefaultDescription
durationDurationrequiredThe amount of time to wait

Examples​

Wait for 2 seconds:

await tt.wait(Duration(seconds: 2));

Wait for 500 milliseconds:

await tt.wait(Duration(milliseconds: 500));

Best practices​

  • If possible use SyncType.settled in proceeding action if you expect animation to conclude.
  • If possible use expect with a timeout e.g. to wait for loaded state.
await tt.type(MyKeys.searchField, 'flutter');
await tt.wait(Duration(milliseconds: 300)); // Wait for debounce
await tt.exists(MyKeys.searchResults[0]);