Illustrative workflow, not a live workspace result.
Claim
A member can save their profile
HTTP response
Page responds
Workflow evidence
No persistence test supplied
Result
Save behavior remains unverified
Checks
A page that loads is not a feature that works.
Compare each claim with the observations behind it. A reachable page proves reachability, and anything the evidence does not support stays visibly unverified.
Checking response...
Illustration of a page check. User journeys need separate test evidence.
Why use Checks?
An agent saying the work is complete is a useful handoff, but it is not the acceptance test. Keep each claim next to the observation that supports it.
Review the claim and its basis
See what was expected and what was actually observed.
Keep untested work visible
A reachable page does not turn an untested signup or payment flow into a pass.
Give the next test a purpose
Use unresolved claims to decide what needs a test, a repair, or a human decision.
How Checks fits your work
01
Describe the behavior
Enter the website URL and the claims you want to check.
02
Collect and supply evidence
Run the HTTP observation and add results from the relevant workflow tests.
03
Review the result
Inspect findings and resolve the remaining claims before approving release.
What to know before you start
The built-in observer checks HTTP responses. Browser interactions, payments, and persistence require separate test evidence.