DevelopmentExtension test cases
Test cases for a browser extension: install, permissions, popup, the pages it works on, settings and updates
Pricefrom $13
Admin panel test casesPrograms
Payment 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
Example for the Standard package
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
An internal tool is used by a few people, but one click can change thousands of records: a bulk edit that also hits hidden rows, an import that overwrites instead of adding, a role that can approve its own request, an action that leaves no trace in the log. We write test cases for the tool you describe: lists, search and filters, creating and editing records, field rules, roles and rights, approvals, bulk actions, imports and exports, the action log and settings. Each case has steps, test data, the expected result and a priority, and the risky ones are marked to run on a copy of the data. 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 log in to your tool or touch your data.
What is included
- What you getAn Excel workbook with the admin cases: ID, area, role, title, preconditions, steps, test data such as an import file with duplicates and a broken row, expected result, priority, a mark for cases to run only on a copy of the data and a column for your result, plus a checklist per area. From Standard, a Word test plan with roles and browsers; in Premium, a full plan, a regression checklist for each release and a bug report template.
- Records and fieldsCreate, edit, required fields and limits
- Roles and rightsWho can see, change and approve what
- Bulk actionsOnly the chosen rows, with a confirmation
- Imports and exportsFormats, duplicates and errors in rows
- Action logEvery change with who and when
How it works
- 1ToolYou send the screens, roles and 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 on a copy of the data
What we need from you
What the tool manages (orders, users, content, stock or other), who uses it and the roles, what each role may do, field rules, approvals, bulk actions, import and export formats, what the action log records, the browsers or systems and what broke before. Screenshots of the screens with made-up data, a feature list or requirements: up to 5 files as images, Word, Excel or PDF. Never send logins or real records.
We will ask you:
- What does the tool manage?
- Which roles are there?
- Which actions are the riskiest?
- What has broken before?
Compare packages
| Packages | Basic25 cases for one admin area$13 | Standard60 cases, up to 4 areas$29 | Premium120 cases, up to 8 areas$60 |
|---|---|---|---|
| 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 | Internal admin tool | Internal admin tool | Internal admin tool |
| 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 admin tool?
No. We write the cases and checklists; your people run them. We never log in to your tool or touch your data.
Our tool has no documentation. Is that a problem?
No. Screenshots of each screen and a few lines on what each button does are enough. The cases follow what you describe, so anything you leave out stays out.
Is this an access audit?
The cases include checks of rights, such as a role trying an action it should not have. They are not a security audit or a penetration test.
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?
Development
DevelopmentAccounting program cases
Test cases for a desktop accounting program: entries, documents, calculations, reports, imports and backups
Pricefrom $13
DevelopmentEditor test cases
Test cases for a desktop editor: files, editing tools, undo, formats, autosave, settings and updates
Pricefrom $13
DevelopmentPricefrom $15