Allow more flexibility for Driver implementations.
Background
Browser-based testing is inherently decoupled, and usually involves some retry/await concept to ensure the rendered web UI is up to date with the server side state.
Wrapping the assertion functions in the Driver protocol allows flexibility for browser-based Drivers:
use built-in framework assertions (Wallaby, Playwright) that have an integrated retry
build custom retry wrapper around PhoenixTest.Assertions
germsvel
commented
2 months ago
Extracted from #74
Goal
Allow more flexibility for Driver implementations.
Background
Browser-based testing is inherently decoupled, and usually involves some retry/await concept to ensure the rendered web UI is up to date with the server side state.
Wrapping the assertion functions in the
Driverprotocol allows flexibility for browser-based Drivers:PhoenixTest.Assertions