Hand off the testing of your next web change.
From your Jira issue and the context already shared with Checktide, we design and run the checks in the environment you authorize, investigate unexpected behaviour, and return human-reviewed findings. You keep the business decisions, the access authorization and the final acceptance.
From your Jira issue, we design and run checks in the environment you authorize, investigate unexpected behaviour and return human-reviewed findings.
You keep the business decisions, the access authorization and the final acceptance.
Explore what a successful-looking action can hide — and the evidence that comes back.
Fictional arcade game. The score is just for play.
Esc · back to the coast
Fictional arcade game. The score is just for play. 45-second round.
Your next change. Verified beyond the surface.
Hand over the work of deciding what to check, running it and investigating the results. Get reviewed findings and evidence back on the Jira issue, ready for your team’s next decision.
We use the context already available to Checktide. Add notes, screenshots or files whenever they help.
With what we may and may not do in them. Pages behind a sign-in are tested with your test account or, where anyone can sign up, our own.
We ask on the issue when a missing business rule or permission affects the work. You keep the business decisions, access authorization and final acceptance.
What a successful-looking action can hide.
A successful cancellation can still leave another customer unable to book. Explore this fictional example to see how Checktide connects a business rule to observed behaviour, evidence and the next action.
Cancellation passed. Immediate release is still unverified.
The cancellation worked, but the slot stayed unavailable to another member. After a fix, it became available within a minute; immediate release is still unverified. The checks for other members’ bookings and paid bookings are also unfinished.
We continue: verify immediate release and check access to another member’s booking, within the original scope at no extra credits.
We need from you: a paid booking we may use. An existing booking is enough.
Not verified means there is not enough evidence for a verdict. The decision to release stays with your team.
Booking #4471 — Court 2, Thu Nov 5, 10:30–11:00, unpaid, ours — cancelled from My bookings. The list and the cancel response were watched; the response said cancelled.
Three looks at the Court 2 schedule — 10:04 after a reload, 10:12 reloaded, 10:22 after signing out and in: the 10:30 slot shown Unavailable each time. The slots response read at 10:22 still named booking 4471, which is cancelled, as holder.
After your fix: a new booking (#4502) cancelled at 2:14; the first look at 2:15, after a reload, showed the slot Available; it was booked as #4503 at 2:19. Nobody watched the minute in between.
Take a closer look.
Explore the findings, their evidence, and what happens after a fix.
Worked exampleSee your site’s subscription, the credits it includes, and the rate for verification work.
PricingCheck installation, permissions and data handling before connecting your site.
Docs & trust