This step waits up to a specified number of minutes for the page to settle and returns as soon as the page becomes idle. It uses the same smart-settle probe as the second-based wait steps, but converts the minute value to milliseconds before passing it to the budget. Settlement requires the DOM to be ready, all network requests to have completed, no pending setTimeout callbacks, and no MutationObserver activity for at least 250 ms.
Use this step for operations that are known to take longer than a few seconds - such as file processing, report generation, or background task completion. The number may be followed by minute, minutes, or the shorthand m. Both I and we pronouns are accepted, and the pronoun may be omitted when chaining with And. Prefer a shorter wait step when the expected duration is only a few seconds, to keep test run times low.
Accepted phrasings
When I wait 1 minute
When I wait 10 minutes
When we wait 1m
And wait 2m
And wait 2 minutes
When we wait 1 minute
Examples
When I wait 1 minute
When I wait 10 minutes
When we wait 1m
And wait 2 minutes
In a real scenario
Scenario: Administrator triggers a bulk export and waits for completion
Given I am logged in as "admin"
When I go to "/admin/reports/export"
And I wait until the page is loaded
And I press "Export All Records"
And I wait 2 minutes
Then I should see "Export complete"
And I should see "Download"