Skip to content

Give the browser assertions a timeout suited to a loaded runner #51

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.

Sign up for GitHub

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

Merged
ivanvyd merged 1 commit into from
Jul 30, 2026
Merged

Give the browser assertions a timeout suited to a loaded runner #51

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions tests/Healthie.Tests.E2E/BrowserFixture.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,14 @@ public async ValueTask InitializeAsync()

_playwright = await Playwright.CreateAsync();
_browser = await _playwright.Chromium.LaunchAsync(new() { Headless = true });

// Playwright's default is five seconds, which is tuned for a developer's machine driving one
// page. Every assertion here waits on a Blazor Server round trip, and the release workflow
// runs this suite straight after eleven hundred unit tests across two frameworks -- a loaded
// runner made assertions that pass on every pull request fail twice during a release, which
// reads as a broken feature rather than a busy machine. Raised once here rather than
// sprinkled per call, so no future assertion has to remember.
Assertions.SetDefaultExpectTimeout(20_000);
}

public async Task<IPage> NewPageAsync()
Expand Down