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 a delivery app several people touch one order: the customer, the restaurant or store, the courier and your support. Bugs live between them: an address just outside the zone, a status stuck on Cooking, a courier who still sees an order the customer cancelled, a fee that changes after a tip. We write test cases for the sides you describe: address and location, zones and fees, the menu or catalog, cart, time slots or as soon as possible, payment in test mode, order statuses and tracking, push notifications, courier actions, cancellations, refunds and ratings. Each case has steps, test data, the expected result 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 the cases; your people run them. We never place orders or use your apps.
What is included
- What you getAn Excel workbook with the delivery cases: ID, side (customer, courier, partner or admin), area, title, preconditions, steps, test data such as an address on the edge of a zone, expected result, priority and a column for your result, plus a checklist per area. From Standard, a Word test plan with devices and who runs which side; in Premium, a full plan, a regression checklist for each release and a bug report template.
- Addresses and zonesZone edges, fees and minimum order
- Order statusesEach change seen by every side
- Courier sideAccepting, picking up, delivering and problems
- Location and mapsPermission off, wrong pin, a moving courier
- Cancellations and refundsAt each status, as your rules say
How it works
- 1SidesYou send the screens of each app and your rules
- 2CasesWe write the cases, checklists and plan from your description
- 3DeliveryYou get the Excel workbook and the Word file on the order page
- 4Your runYour people run each side and note the results
What we need from you
Which apps or sides exist (customer, courier, restaurant or store, admin), what is delivered, how zones and fees are set, the minimum order, time slots or as soon as possible, payment methods and tips, the order statuses and who changes each, the pushes sent, your rules for cancellations and refunds, the platforms and versions and what broke before. Screenshots of each screen on every side: up to 5 files as images, Word, Excel or PDF. Never send logins or real customer addresses.
We will ask you:
- What do you deliver, and to whom?
- Which sides should the cases cover?
- How are zones and fees set?
- What has broken before?
Compare packages
| Packages | Basic25 cases for one delivery step$13 | Standard60 cases, up to 4 areas$30 | Premium120 cases, up to 8 areas$60 |
|---|---|---|---|
| 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 | Delivery app | Delivery app | Delivery app |
| 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 app?
No. We write the cases and checklists; your people run them. We never place orders, deliver or log in to any of your apps.
Can one package cover the customer and courier apps?
Yes. Each side counts as an area in your package: Standard covers up to 4 areas and Premium up to 8, so you choose how to split them.
Can you cover maps and location?
Yes, as cases your people run with location on and off, a wrong pin or a simulated route. We do not track or move anyone.
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?


