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
A shopping app has troubles a website does not: a call arrives during payment, the connection drops in a lift, a push about a sale opens the home screen instead of the product, the cart empties after an app update. We write test cases for the app you describe on iPhone and Android: catalog and search, the product screen, cart and wishlist, checkout and in-app payment in test mode, account and orders, push notifications and deep links, permissions, poor connection, interruptions, screen sizes and updates. Each case has steps, test data, the expected result and a priority. Send screenshots of each screen and the system versions you support. 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. We never install or use your app.
What is included
- What you getAn Excel workbook with the app cases: ID, area, platform, title, preconditions, steps, test data, expected result, priority and a column for your result, plus a checklist per area. From Standard, a Word test plan with your phones, tablets and system versions; in Premium, a full plan, a regression checklist for every app release and a bug report template.
- Catalog and cartSearch, variants, wishlist and the saved cart
- Payment in the appThe cards and wallets you offer, in test mode
- Push and deep linksEach one opens the right screen
- InterruptionsCalls, background, poor or lost connection
- Devices and updatesScreen sizes, system versions and app updates
How it works
- 1AppYou send the screens, platforms and versions
- 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 your devices and note the results
What we need from you
iOS, Android or both and the oldest versions you support, phones and tablets, the areas to cover, payment methods in the app and the provider, the push notifications you send and where each should lead, deep links from emails or ads, the permissions the app asks for, what works without internet and what broke before. Screenshots of every screen: up to 5 files as images, Word, Excel or PDF. Never send logins, store account access or customer data.
We will ask you:
- iOS, Android or both?
- Which areas matter most?
- Which pushes and links do you send?
- What has broken before?
Compare packages
| Packages | Basic25 cases for one app 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 | Mobile shopping app | Mobile shopping app | Mobile shopping 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; you or your people run them on your devices. We never install, use or test your app.
Which devices do the cases cover?
The ones you name. From Standard, the test plan lists them with system versions and says which cases to repeat on each.
Will the cases help pass store review?
They check how the app works, which helps, but store review follows the stores' own rules, and we cannot promise approval.
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?


