You hand over the change. We take on the checks.
From the Jira issue you already have, we design the checks, run them in the environment you authorize, investigate what doesn’t match, and a person brings reviewed evidence back to the same issue.
Your part. Our work. The next step.
Hand over
Yours · at the startWe verify and investigate
Ours · the bulk of the workUse the result — and follow through
Yours to decide · ours to continue- Your Jira issue for the agreed change — we reuse the context already shared with Checktide.
- The environment and test accounts you name, and what we may do in them — the access stays yours, including any later widening.
- Notes, screenshots and files are optional: volunteer them whenever you like, without waiting for a question.
We ask on the same issue when we need a business rule, missing context or permission to continue. You do not need to write test cases or approve each routine check.
- Read the report in the Checktide panel; a short comment tells you it is ready.
- Decide what to fix and whether to release — a report is evidence, not a release.
- After your fix, request the included retest from the report.
- Read the issue and the available context.
- Design the checks: what to check, which roles and conditions matter, where to run each and as whom — you do not write test cases.
- The checks appear in the Checktide panel on the issue.
- Walk the checks in the environment you authorized, as the accounts you named.
- Investigate what doesn’t match until the evidence tells the problem apart — not a promise of every root cause.
- A person reviews every verdict against its evidence: Passed, Failed or Not verified.
- Deliver the report on the same issue, with what is still open and who carries it.
- Continue agreed unfinished work in the original scope — unless it needs something only you can give.
- Run the included retest: one, same scope, requested within 14 days of delivery; a retest that reaches no result does not use it.
- Oct 27
The issue, written with the initial permission: sign in and view as Member A or B; cancel bookings we create as Member A; no payments.
- Oct 27
Environment staging.courtline.example; Member A and Member B, your test accounts.
- Oct 28 · 9:41 AMoriginal run
Four checks, in the issue’s own words, appeared in the Checktide panel.
- Oct 28 · 9:48 → 9:55 AM
Asked on the issue: may we create a booking as Member B for check 03? Your answer: “Not now. Use existing data only.”
- Oct 28 · 10:02–10:22 AM
Walked as Member A, then as Member B; the slots response read at 10:22 AM.
- Oct 28 · 10:31 AM
Reviewed by a person; report ready on the issue.
✓01 Passed✕02 Failed?03 Not verified?04 Not verified
- Nov 2
Your fix deployed. From the report you widened the permission: create and cancel unpaid bookings as Member A or B; payments still not permitted. You requested a retest of check 02.
- Nov 3 · 2:14–2:41 PMretest · check 02 only
Free a minute after the cancellation, but not shown to be released straight away: check 02 Not verified. It reached no result, so the included retest was not used. 01, 03 and 04 were not retested and keep their Oct 28 marks.
?02 Not verified · Nov 3 - Still open
02 and 03: ours to continue in the original scope, no extra credits. 04: needs a paid booking we may use — an existing one is enough; only if one had to be made would we need permission for one test payment.
02 · 03 ours04 needs from you
An illustrative chronology of one fictional issue, not a promise of completion time. Inspect it on the worked example →
From handover to follow-through.
See what happens after you hand over a change, including where we may need your input.
- 01YoursHand over
Your Jira issue for the agreed change, with any context already available to Checktide; the environment and test accounts you name, and what we may do in them. Extra notes, screenshots and files are optional. Add them whenever they help.
- 02OursRead, design the checks
From the issue and the available context: what to check, which roles and conditions matter, where to run each check and as whom. The checks appear in the Checktide panel on your issue — you do not write test cases, and you are not asked to approve each routine check.
- 03TogetherScope and permissions
The checks and the actions we intend to take in your environment are visible in the Checktide panel. You widen or narrow what we may do — a permission decision, not a sign-off on each routine check.
- 04OursWalk the checks, investigate
In the environment you authorized, as the accounts you named. What doesn’t match the issue’s words is looked into for evidence that tells the problem apart — not a promise of every root cause.
- 05OursA person reviews; the report goes on the issue
Every verdict against its evidence: Passed, Failed or Not verified per check, with cases, observations, responses and what is still open. The report lives in the Checktide panel; a short comment tells you it is ready.
- 06YoursYour fix, your decisions
You keep the goals, the authorization, the business judgement, the fix and the decision to release. A report is evidence, not a release.
- 07TogetherSame-scope follow-through
After your fix, one retest of the same scope requested within 14 days of delivery is included; a retest that reaches no result does not use it. What is still open after a report stays in it with its reason and who carries it — ours to continue in the original scope, unless it needs something only you can give.
Which work can you hand over?
What one change can be
A web feature or fix can involve several roles, business rules, steps and state changes. We design the checks around the change agreed in your Jira issue.
The service covers web verification through Jira Cloud. It does not include code fixes, native mobile or game testing, or unlimited whole-site QA.
The included retest
After you fix what a report found, one retest of the same scope requested within 14 days of delivery uses no credits. Request it from the report. A retest that reaches no result does not use it. Asking us to re-check a verdict against its evidence is free and does not use the included retest.
What a report is
Evidence a person has checked — not a release, and not a guarantee that a change is bug-free. The decision to ship stays yours.
Not verified means no supported verdict; it is never a pass, and a later stage never upgrades an earlier mark.