DevelopmentPayment protectionDetails
- Revisions within the package are free.
- If you do not respond within 3 days of delivery, the work is accepted automatically.
The money is reserved when you pay and released only once you accept the work.

Example result
Test cases: sign-up, cart and checkout of a small online tea shop
Cases from the "Checkout" area (4 of 18)
| ID | Title | Steps | Test data | Expected result | Priority |
|---|---|---|---|---|---|
| CO-01 | Order with a card, standard delivery | 1. Add 2 teas to the cart. 2. Open the cart, press Checkout. 3. Fill in the address, choose standard delivery. 4. Pay with the test card. | Test card from the payment provider's sandbox | The order page shows the number; a confirmation email arrives within 5 minutes | High |
| CO-04 | Free delivery threshold | 1. Add teas for $39.90. 2. Open checkout. 3. Add one more tea. | Shop rule: free delivery from $40 | Delivery shows $4.90, then $0.00 after step 3 | High |
| CO-09 | Postcode left empty | 1. Fill in every field but the postcode. 2. Press Pay. | — | The form is not sent; the postcode field is marked with a clear message | Medium |
| CO-15 | Back button after paying | 1. Pay for an order. 2. Press the browser's Back button. | — | No second charge; the cart is empty | High |
Checklist: cart (part)
- The quantity can be changed with + and − and typed in
- Removing the last item shows an empty cart message
- The cart is kept after closing the tab and coming back
- Prices and the total match the product pages
Files: an Excel workbook with the cases, a Result column and the checklists, and a Word file with the test plan. We write the cases from the description and screenshots; the shop's own people run them.
Client: Leaf & Kettle, an online shop selling about 80 kinds of loose tea, on its own site. Task: cases the shop owner and an assistant can go through before each update. Standard package: 60 cases in up to 4 areas, checklists and a short test plan. Excerpt below.
The client and all details are made up.
About this service
In accounting software a bug is a wrong number in a report someone signs: rounding that differs between the invoice and the total, a closed period that can still be edited, an import that skips a row without a word, a backup that cannot be restored. We write test cases for the program you describe: documents and entries, calculations with taxes and currencies as your rules set them, reports and their totals, period closing, user rights, imports and exports, printing, backups, installation and updates on the systems you name. Each case has steps, test data with made-up figures and expected totals worked out from your rules, and a priority. You get an Excel workbook; from Standard a Word test plan, and in Premium a regression checklist and a bug report template. We write; you run. The cases do not check that your rules meet tax law and are not accounting advice.
What is included
- What you getAn Excel workbook with the program cases: ID, area, title, preconditions, steps, test data with made-up documents and the expected totals, expected result, priority and a column for your result, plus a checklist per area. From Standard, a Word test plan with systems, a test copy of the database and the order of work; in Premium, a full plan, a regression checklist for every update and a bug report template.
- Documents and entriesCreate, edit, cancel and copy
- CalculationsTaxes, currencies and rounding by your rules
- ReportsTotals that match the documents behind them
- Periods and rightsClosing, locking and who can change what
- Files and backupsImport, export, printing, backup and restore
How it works
- 1ProgramYou send screens, rules and sample documents with made-up data
- 2CasesWe write the cases, checklists and plan from your description
- 3DeliveryYou get the Excel workbook and the Word file on the order page
- 4Your runYou run the cases on a test copy of the database
What we need from you
What the program does and for whom, the Windows or macOS versions, the areas to cover, how taxes, currencies and rounding are calculated as set in the program, the reports and how their totals are made, period closing and user rights, import and export formats, printing, backup and update steps and what broke before. Screenshots and sample documents or reports with made-up figures: up to 5 files as images, Word, Excel or PDF. Never send real company books or client data.
We will ask you:
- What does the program do?
- Which areas matter most?
- How are taxes and rounding set?
- Which systems do you support?
- What has broken before?
Compare packages
| Packages | Basic25 cases for one program area$13 | Standard60 cases, up to 4 areas$31 | Premium120 cases, up to 8 areas$61 |
|---|---|---|---|
| Deadline | 1 day | 2 days | 4 days |
| Revisions | 1 | 2 | 3 |
| Test cases | 25 | 60 | 120 |
| Areas or features | 1 | up to 4 | up to 8 |
| Checklists | 1 | up to 4 | up to 8 |
| Test plan | No | short | full |
| Regression checklist and bug report template | No | No | Yes |
| Product | Desktop accounting program | Desktop accounting program | Desktop accounting program |
| Order Basic | Order Standard | Order Premium |
Payment protection
You pay when you order, but the money is released only for accepted work.
- Fixed priceThe package price does not change after you pay.
- The money is reservedWhen you pay, the amount is only reserved. It is released to the service once you accept the work.
- Checked before deliveryEvery result goes through a quality check before it reaches you, and you see it on the order page before accepting it.
- Free revisionsAsk for changes within your brief as many times as the package allows.
- Acceptance after 3 daysIf within 3 days of delivery you neither accept the work nor ask for changes, it is accepted automatically. If you write in the order chat after delivery, the order waits; once we answer, we may start the 3 days again and will say so in the chat.
- Redo or a full refundIf the result does not match your brief and the revisions did not fix it, or the work takes more than twice its deadline, write in the order chat: we will redo the work or refund the payment in full.
Questions and answers
Will you test my program?
No. We write the cases and checklists; you or your people run them. We never install, open or use your program.
Do the cases check that our tax calculations are legal?
No. We take your rules as you give them and check that the program follows them. Whether the rules are right is a question for your accountant or tax adviser.
Which data should we run the cases on?
On a test copy of the database with made-up documents, never on live books. The test data in the cases is made up for that.
Can you cover installation and updates?
Yes, from what you describe: a clean install, an update over an old version, the database after the update and a rollback.
Do test cases mean the product has no bugs?
No. They cover what you describe at the depth of your package; bugs outside the cases can remain, and the result depends on how carefully the cases are run.
Did not find your answer?


