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
Social and chat apps are checked by two or more people at once: a message sent offline and delivered twice, a blocked user who still sees the profile photo, a muted group that wakes the phone at night, a deleted photo that stays in a reply. We write test cases for what you describe: profiles, the feed or chats, private and group messages, read receipts, media and voice notes, notifications, privacy settings, blocking, reports, moderation and one account on several devices. Many cases need two or three test accounts, and each case says who does what. Each 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; your people run them. We never join, post or send messages in your app.
What is included
- What you getAn Excel workbook with the app cases: ID, feature, title, accounts needed (user A, user B, a blocked user), preconditions, steps, test data, expected result for each account, priority and a column for your result, plus a checklist per feature. From Standard, a Word test plan with devices and how many test accounts to prepare; in Premium, a full plan, a regression checklist for each release and a bug report template.
- MessagesSent, delivered, read, edited and deleted
- GroupsInvites, roles, leaving and muting
- MediaPhotos, video, voice notes and size limits
- Privacy and blockingWho sees what, and what a block stops
- Several devicesOne account on a phone and a computer
How it works
- 1FeaturesYou send the screens and your privacy 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 the cases with test accounts
What we need from you
The platforms (iOS, Android, web, desktop), the features to cover, privacy settings and who can see or message whom, group sizes and roles, media types and size limits, notification settings, how blocking, reports and moderation work, rules for editing and deleting messages, whether one account works on several devices and what broke before. Screenshots of each screen: up to 5 files as images, Word, Excel or PDF. Never send real users' messages, photos or account data.
We will ask you:
- What kind of app is it?
- Which features matter most?
- Who can see and message whom?
- Which platforms?
Compare packages
| Packages | Basic25 cases for one feature$13 | Standard60 cases, up to 4 features$30 | Premium120 cases, up to 8 features$59 |
|---|---|---|---|
| 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 | Social or chat app | Social or chat app | Social or chat 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 with test accounts. We never sign up, post or message in your app.
Why do the cases need several accounts?
Most of what can go wrong happens between people: delivery, read receipts, blocks and privacy. Each case names the accounts it needs and what each one should see.
Do the cases check our moderation rules?
They check that reports, blocks and hidden posts work as you describe. What is allowed on your platform and how reports are judged are your decisions.
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?


