High-value candidates are:
Prefer role/name or stable test selectors.
Assert a meaningful UI state, URL, network response, or application state—not merely “the click happened.”
Do not solve it with unlimited retries.
Look for dynamic time/data, animation, race conditions, weak locators, external dependencies, and shared state.
Builder: minimal test diff, actual A/B red/green runs, stability rationale and coverage limit.
Foundation: precise assertion design with predicted A/B results; execution explicitly unverified.
The verifier owns review—not just typing.
A green test means one specified behavior passed under known conditions.
It does not prove the whole product is ready.
What makes your regression check deterministic?