Problem
visit uses browsingContext.navigate with wait: "complete" and the default 10s send_command timeout. Under concurrent load (6 feature tests with 9+ browser tabs), the auth callback → redirect → LiveView mount chain can exceed 10s.
Passes most runs but fails intermittently (2 of 6 feature tests).
Suggestion
Either:
- Increase navigate timeout to 30s (it's a page load, not an interaction)
- Use
wait: "interactive" instead of wait: "complete" — fires after DOM is ready, doesn't wait for all resources (fonts, images)
- Make navigate timeout configurable via
config :wallabidi, navigate_timeout: 30_000
Problem
visitusesbrowsingContext.navigatewithwait: "complete"and the default 10ssend_commandtimeout. Under concurrent load (6 feature tests with 9+ browser tabs), the auth callback → redirect → LiveView mount chain can exceed 10s.Passes most runs but fails intermittently (2 of 6 feature tests).
Suggestion
Either:
wait: "interactive"instead ofwait: "complete"— fires after DOM is ready, doesn't wait for all resources (fonts, images)config :wallabidi, navigate_timeout: 30_000