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 fitness app is used mid-workout, with the screen locked and music playing, so the checks are different: does the timer keep going in the background, does the rest screen survive a phone call, are kilos and pounds converted the same everywhere, does one missed day break the streak. We write test cases for what you describe: onboarding questions, workout plans, the exercise player with timers and sounds, logging sets, progress and streaks, sync with health apps or watches, reminders, subscriptions and offline use. 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; you or your people run them. The cases check that the app works as described, not whether the workouts or numbers are right for anyone's health.
What is included
- What you getAn Excel workbook with the app cases: ID, area, title, preconditions, steps, test data such as a user switching from kilos to pounds mid-plan, expected result, priority and a column for your result, plus a checklist per area. From Standard, a Word test plan with phones, watches and system versions; in Premium, a full plan, a regression checklist for each release and a bug report template.
- Workout playerTimers, sounds, pauses and the locked screen
- Logging and progressSets, units, streaks and charts
- Health apps and watchesSync with the services you name
- RemindersTime zones, silent mode and permissions turned off
- SubscriptionsTrials, renewals and restoring a purchase, in test mode
How it works
- 1AppYou send the screens, features and connected services
- 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 phones and watches
What we need from you
iOS, Android or both and the versions, the areas to cover, how plans are built from onboarding answers, units and how they convert, timer and sound settings, the health apps or watches you connect to (e.g. Apple Health or Health Connect), the reminders, the subscription plans and trial, what works offline and what broke before. Screenshots of each screen: up to 5 files as images, Word, Excel or PDF. Never send logins or real users' health data.
We will ask you:
- What does the app do?
- Which devices and services does it connect to?
- How do subscriptions work?
- What has broken before?
Compare packages
| Packages | Basic25 cases for one app area$13 | Standard60 cases, up to 4 areas$29 | Premium120 cases, up to 8 areas$58 |
|---|---|---|---|
| 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 | Fitness app | Fitness app | Fitness 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. We never install or use your app or connect any device.
Do the cases check the workouts or calorie numbers?
No. They check that the app shows and counts what you specify. Whether a plan or a calorie figure is right for a person is a matter for a qualified trainer or doctor, not for test cases.
Can you cover sync with watches?
Yes, as cases your people run on their own devices for the services you name: what is sent, when, and what happens when sync is off.
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?


