- Home
- Skills
- Testing & Debugging
- Test Handover — an acceptance report that proves it's done
More screenshots
Works with the AI Agents you already use
Test Handover — an acceptance report that proves it's done
Maps every agreed feature to tests that were actually run, records expected vs actual with evidence, re-verifies fixes, and ends with a sign-off page your client can accept feature by feature.
$5
Test Handover — an acceptance report that proves it's done
Example session with this skill installed
Write an acceptance report for my client. The scope is in SPEC.md; run the tests and tell me what's really done.
- Read your context and instructions
- Compiled the test handover
Bean & Kettle back office: Test and acceptance report
Build tested back office v1.0 ·
Environment local test copy with fictional sample data ·
Test date 2026-11-09 ·
For the shop owner
Fictional example. Every result below comes from a real run of the included tests and a scripted browser walk-through.
Summary
| Features in scope | 6 (from the agreed scope) |
| Results | 2 Pass · 3 open defects · 1 moved to phase 2 |
| Automated tests (business rules) | first run 9 passed, 3 failed → after fixes 12 passed, 0 failed |
| Browser walk-through (screens) | 6 checks: 3 passed, 3 failed |
| Defects found | 5: 2 fixed and re-verified; 3 open, scheduled for fixing before go-live |
| Moved to phase 2 | 1: order confirmation email (F6), agreed with the client |
Verdict: F1 and F2 are ready for acceptance now. F3, F4 and F5 are accepted once defects #3–#5 are fixed and re-tested, scheduled before go-live. F6 moves to phase 2, as agreed with the client.
Feature checklist
| ID | Feature | Result | How verified |
|---|---|---|---|
| F1 | Order total = sum of its lines | ✅ Pass | automated test |
| F2 | Discount codes (percentage, never below 0, expired refused) | ✅ Pass after fix | automated tests; defect #2 fixed |
| F3 | Monthly revenue report (paid + shipped, no test accounts) | ❌ Open: defect #5 | calculation passes after fixing defect #1; the Revenue screen is not connected to it |
| F4 | Roles: staff view orders; only owner sees revenue and edits prices | ❌ Open: defect #4 | role rules pass; sign-in accepts any password |
| F5 | Refunds (paid/shipped only, owner only) | ❌ Open: defect #3 | refund rules pass; the refund is not saved on screen reload |
| F6 | Order confirmation email | ⬜ Phase 2 | not in this build; moved to phase 2 |
Round 1: rules and calculations
| Check | Expected | Actual (first run) | Result |
|---|---|---|---|
| Order of 2 × 16.00 + 1 × 48.00 | 80.00 | 80.00 | ✅ |
| 10% code on 80.00 | 72.00 | 72.00 | ✅ |
| 120% code on 50.00 | 0 (never below 0) | −10.00 | ❌ defect #2 |
| Expired code | refused | refused | ✅ |
| October revenue | 86 orders · 10,981.00 (independent count) | 92 orders · 11,674.00 | ❌ defect #1 |
| Refund a paid order | status becomes refunded | refunded | ✅ |
| Refund a cancelled order | refused | refused | ✅ |
Round 2: who can do what
| Role | Action | Expected | Actual | Result |
|---|---|---|---|---|
| staff | view orders | allowed | allowed | ✅ |
| staff | open revenue report | refused | refused ("owner-only") | ✅ |
| staff | edit prices | refused | refused | ✅ |
| staff | refund an order | refused | refused ("owner-only") | ✅ |
Round 3: back-office screens (browser)
| Check | Expected | Actual | Result |
|---|---|---|---|
| Staff sees only the Orders menu | no Revenue menu, no Refund button | as expected | ✅ |
| Refund button hidden on cancelled orders | hidden | hidden | ✅ |
| Owner refunds order #754 | status refunded, confirmation message | as expected | ✅ |
| Order #754 after reloading the page | status stays refunded | status back to paid | ❌ defect #3 |
| Sign in with a wrong password | refused | signed in as Owner | ❌ defect #4 |
| Revenue screen follows the revenue calculation | live figures | figures fixed in the page | ❌ defect #5 |
Defects
#1 Revenue report counted refunded orders · Major · ✅ fixed
What happened: October revenue showed
11,674.00 from 92 orders; the correct figure is
10,981.00 from 86 orders. The difference is exactly the 6 refunded October orders (693.00).
- After fix: 86 orders · 10,981.00, matches the independent count ✅
#2 Discount could make a total negative · Minor · ✅ fixed
What happened: a code above 100% turned a 50.00 order into
−10.00. No such code exists today, so no real order was affected.
- After fix: total is 0.00 ✅
#3 Refund is not saved · Major · open, fix before go-live
- Reproduce: owner → Orders → #754 → Refund order → Yes, refund → reload the page → open #754.
- Agreed action: save the refunded status to the shop database; re-test before go-live.
#4 Sign-in accepts any password · Blocker · open, fix before go-live
Security impact: yes. Anyone who knows an account email can sign in. The back office must not be published before this is fixed.
- Agreed action: server sign-in with stored, hashed passwords; re-test before go-live.
#5 Revenue screen shows fixed figures · Major · open, fix before go-live
- Agreed action: connect the screen to the revenue calculation; re-test before go-live.
Not tested
| ID | Feature | Current state | Agreed action |
|---|---|---|---|
| F6 | Order confirmation email | This build contains no code that sends email. | Built and tested in phase 2. |
Sign-off
| ID | Feature | Accepted | Not accepted | Comment |
|---|---|---|---|---|
| F1 | Order total | ☐ | ☐ | |
| F2 | Discount codes | ☐ | ☐ | |
| F3 | Monthly revenue report | ☐ | ☐ | after defect #5 is fixed |
| F4 | Roles | ☐ | ☐ | after defect #4 is fixed |
| F5 | Refunds | ☐ | ☐ | after defect #3 is fixed |
Delivered as test-handover.md plus a print-ready HTML with a signature block; a developer appendix lists suite output, causes and fixes.
Connects securely to your tools. The creator never sees your data.
About this skill
"Is everything working?" is the question that holds up your final invoice. Test Handover answers it with evidence instead of a promise.
- Starts from the agreed scope (spec, quote, ticket list) so every feature appears, including the ones nobody tested.
- Runs and records: your automated suite, permission checks per role, main flows, edge cases. Each check gets expected · actual · result · how it was verified.
- Defects the client can follow: what happened, what should happen, how to reproduce, severity, and whether it's a security issue.
- Fix round: re-runs failed checks after you fix them and shows before/after.
- Sign-off page: Accepted / Not accepted per feature, ready to sign.
- Developer appendix: suite output, causes and fixes, kept out of the client's way.
The one rule: it never reports a test that wasn't run. No evidence means Not tested, with the reason. That's what makes the report worth signing.
The included example is a real run on a small fictional shop: 12 automated tests (9 passed on the first run, 12 after two fixes) plus a browser walk-through that records three open defects, one of them a sign-in that accepts any password, each with severity, reproduce steps and the agreed action.
Every report also comes as a styled single-file HTML, print-ready for PDF. Writes in your language (English, Chinese, Japanese and more).
Works with Claude Code, Codex CLI, Gemini CLI, Cursor and other agents that can read files and run shell commands.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Testing & Debugging.
Only as complete as your tests and environment allow; features that can't be exercised are listed as Not tested rather than guessed.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 8 days ago
- Software
Python
Permissions
Runs your test suite and, if available, a browser walk-through against your local or test environment; writes the report into your project folder. It does not change application code while testing.