ExUnit-style assertions backed by Fluffy.Expect.

Use this module after use ExUnit.Case (or your application's case module) to replace the conflicting ExUnit imports:

use ExUnit.Case
use Fluffy.Assert

import Fluffy
import Fluffy.Locator

Inside a test with an initialized session:

session
|> assert(visible(by_text("Creature registered")))
|> refute(page_title("Error"))

Locator constructors take a locator. Page constructors target the active page; captured-result constructors take the capture key first. All constructors return Fluffy.Expect values, not booleans.

Ordinary ExUnit assertions, including custom messages and pattern matching, retain ExUnit semantics. With a typed expectation as the second argument, assert/2 executes it and refute/2 executes its negation. Both return the updated session. A third argument supplies expectation options.

Negation retains the driver's retry and missing-element semantics. Refuting visibility accepts an absent or hidden element; use count(locator, 0) for absence. Static and Live drivers check structural visibility, while Playwright checks rendered visibility. Refutation does not turn driver errors into success.