Skip to content
tflw

Matchers reference

Every row of tflw's closed matcher set — generated from packages/lang/src/spec-data.ts, the same manifest that regenerates SPEC.md §6.2. not negates any of them, and is is an optional copula that may sit on either side of it — so is not visible, not is visible, is visible and not visible all parse. Every matcher operand below takes the full value grammar, not just literals: has count {expected} works exactly like equals {expected}. See Assertions in depth for the full walkthrough.

equals

Section titled “equals”

any value

expect status equals 201

contains

Section titled “contains”

stringsarrays

expect body.msg contains "created"

matches "<regex>"

Section titled “matches "<regex>"”

strings

expect header "content-type" matches "json"

matches subset {...}

Section titled “matches subset {...}”

objects

expect body matches subset { type: "about:blank", status: 422 }

matches schema "Name" from "src"

Section titled “matches schema "Name" from "src"”

objects

expect body matches schema "ProductResponseDto" from "/openapi.json"

matches file "<path>"

Section titled “matches file "<path>"”

body bytes

expect body bytes matches file "expected-receipt.pdf"

is greater than / is less than

Section titled “is greater than / is less than”

numbersduration

expect body.total is less than 100

has count <value>

Section titled “has count <value>”

arraysUI listsbody bytes

expect body.items has count 3

has count at least <value>

Section titled “has count at least <value>”

arraysUI listsbody bytes

expect body.items has count at least 1

has count at most <value>

Section titled “has count at most <value>”

arraysUI listsbody bytes

expect body.items has count at most 50

is empty / is not empty

Section titled “is empty / is not empty”

stringsarraysobjects

expect body.errors is empty

has value

Section titled “has value”

UI fields

expect field "Email" has value "a@b.c"

is visible/hidden/enabled/disabled/checked

Section titled “is visible/hidden/enabled/disabled/checked”

UI locators

expect button "Pay" is enabled

connects

Section titled “connects”

request

expect request connects

fails / fails matching "<regex>"

Section titled “fails / fails matching "<regex>"”

request

expect request fails matching "certificate"

was made

Section titled “was made”

request to "<url>"

expect request to "/api/orders" was made

has no [minor/moderate/serious/critical] a11y violations

Section titled “has no [minor/moderate/serious/critical] a11y violations”

page

expect page has no critical a11y violations

has no [minor/moderate/serious/critical] security violations

Section titled “has no [minor/moderate/serious/critical] security violations”

response

expect response has no serious security violations

has no [minor/moderate/serious/critical] authorization violations

Section titled “has no [minor/moderate/serious/critical] authorization violations”

response

expect response has no authorization violations

has no [minor/moderate/serious/critical] input handling violations

Section titled “has no [minor/moderate/serious/critical] input handling violations”

response

expect response has no input handling violations

matches snapshot "<name>" [mask <locator>]*

Section titled “matches snapshot "<name>" [mask <locator>]*”

pageUI locators

expect page matches snapshot "checkout-page" mask css ".timestamp"