Skip to content

visit navigate timeout too tight at 10s for concurrent tests #8

@pinetops

Description

@pinetops

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:

  1. Increase navigate timeout to 30s (it's a page load, not an interaction)
  2. Use wait: "interactive" instead of wait: "complete" — fires after DOM is ready, doesn't wait for all resources (fonts, images)
  3. Make navigate timeout configurable via config :wallabidi, navigate_timeout: 30_000

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions