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 blog or CMS site usually breaks after a routine change: a plugin or theme update, a new author with the wrong rights, a post scheduled in the wrong time zone. We write test cases for the site you describe on WordPress or another CMS: creating, scheduling and editing posts, author and editor roles, categories and tags, menus, search, comments and spam settings, media, forms, SEO fields such as titles and redirects, and the pages readers see on phones and computers. Each case has steps, test data, the expected result and a priority. Send a link, screenshots of the admin screens you use and a list of plugins. You get an Excel workbook; from Standard a Word test plan, and in Premium a regression checklist to repeat after each update and a bug report template. We write; you run. We never log in to your admin panel.
What is included
- What you getAn Excel workbook with the site cases: ID, area, role, title, preconditions, steps, test data such as a post with a long title and an embedded video, expected result, priority and a column for your result, plus a checklist per area. From Standard, a Word test plan with devices and browsers; in Premium, a full plan, a regression checklist for every plugin, theme or CMS update and a bug report template.
- PublishingDrafts, scheduling, edits and previews
- RolesWhat authors, editors and admins can do
- Navigation and searchMenus, categories, tags and archives
- Comments and formsModeration, spam settings and messages sent
- After updatesWhat to recheck when a plugin or theme changes
How it works
- 1SiteYou send a link, admin screenshots and the plugins
- 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 after each update and note the results
What we need from you
The CMS (WordPress, Ghost, Drupal or another) and its theme, the list of plugins or extensions, the roles of people who publish, the site areas to cover, how posts are scheduled and in which time zone, comment and form settings, languages, the SEO settings and redirects you use, the devices and browsers and what broke after past updates. Screenshots of the admin screens and public pages: up to 5 files as images, Word, Excel or PDF. Never send admin logins.
We will ask you:
- Which CMS and theme?
- Who publishes, and with which roles?
- Which areas matter most?
- What broke after past updates?
Compare packages
| Packages | Basic25 cases for one site area$13 | Standard60 cases, up to 4 areas$29 | Premium120 cases, up to 8 areas$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 | Blog or CMS site | Blog or CMS site | Blog or CMS site |
| 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 site?
No. We write the cases and checklists; you or your people run them. We never log in to your admin panel or change anything on the site.
Can the cases cover SEO?
They check that titles, descriptions, redirects and the sitemap come out as you set them. They are not an SEO audit and do not promise any positions in search.
Will you update my plugins?
No. Updates stay with you; the regression checklist in Premium tells you what to recheck after each one.
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?


