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 landing page has one job, and small faults stop it: a form that accepts a broken phone number, a button that scrolls nowhere on a phone, a thank-you page that never sends the conversion event. We write test cases for the page you describe: the form and its checks, every button and link, anchors and pop-ups, the layout on the screen sizes you name, the cookie banner, the thank-you page and the analytics events you list. Each case has steps, test data, the expected result and a priority. Send a link or screenshots, the form fields and where leads go. You get an Excel workbook with cases and checklists; from Standard a Word test plan for launch day, and in Premium a regression checklist and a bug report template. We write; you or your people run the cases. We never submit your form or check the page ourselves.
What is included
- What you getAn Excel workbook with the page cases: ID, block, title, preconditions, steps, test data such as a phone number in the wrong format, expected result, priority and a column for your result, plus a checklist per area. From Standard, a Word plan for launch day with the devices and browsers you name; in Premium, a full plan, a regression checklist to repeat after every edit of the page and a bug report template.
- Form checksRequired fields, phone and email formats, double sends
- Buttons and linksAnchors, pop-ups, outside links and messengers
- Mobile layoutThe screen sizes and browsers you name
- Leads arriveThank-you page, email or CRM, as you describe
- Analytics eventsChecks that the events you list are sent
How it works
- 1PageYou send a link or screenshots and the form fields
- 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 before launch and after each edit
What we need from you
A link to the page or screenshots of each block on a computer and a phone, the form fields and which are required, where a lead goes (email, CRM, Telegram, Google Sheets), the thank-you page or message, the analytics and ad pixels you use and the events they should record, pop-ups and timers, languages or page variants, and the devices and browsers that matter. Up to 5 files as images, Word, Excel or PDF. Never send logins to your site builder or CRM.
We will ask you:
- What is the page for?
- What does the form ask, and where do leads go?
- Which events should analytics record?
- Which devices and browsers matter?
Compare packages
| Packages | Basic25 cases for one page 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 | Landing page | Landing page | Landing page |
| 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 landing page?
No. We write the cases and checklists; you or your people run them and note what passes. We never submit your form or click through the page ourselves.
Can the cases check that conversions are tracked?
They tell your people how to see whether each event you list is sent, for example in your analytics' real-time or debug view. We do not open your analytics or ad accounts.
Do the cases judge the text or the design?
They check that everything works and shows correctly: no broken layout, overlapping blocks or missing images. Whether the offer convinces visitors is a different question.
Does the site builder matter?
No. The cases follow what the page does, whether it is built on Tilda, WordPress, Webflow or by hand; we use the builder's names for things if you give them.
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?


