DevelopmentAccounting program cases
Test cases for a desktop accounting program: entries, documents, calculations, reports, imports and backups
Pricefrom $13
Extension 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
A browser extension lives on other people's pages, so it breaks when they change: a button added twice on a page that loads content as you scroll, a popup that loses settings after a browser restart, an update that asks for new permissions and gets switched off. We write test cases for the extension you describe: install and first run, permissions, the popup and options page, what it does on the sites you list, keyboard shortcuts, sync between devices, private windows, other extensions running alongside, updates and removal, in Chrome, Firefox, Edge or Safari as you name. 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. We never install your extension.
What is included
- What you getAn Excel workbook with the extension cases: ID, feature, browser, title, preconditions, steps, test data such as a page that loads content as you scroll, expected result, priority and a column for your result, plus a checklist per feature. From Standard, a Word test plan with browsers, versions and sites; in Premium, a full plan, a regression checklist for every release or site change and a bug report template.
- Install and permissionsFirst run, permissions asked and refused
- Popup and optionsSettings kept after a restart
- Pages it works onThe sites you list, scrolling and slow loading
- BrowsersThe ones you name, normal and private windows
- Updates and removalNew permissions, data kept or cleared
How it works
- 1ExtensionYou send the screens, sites and browsers
- 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 or your people run the cases in each browser
What we need from you
What the extension does, the browsers and versions, the permissions it asks for, the sites or kinds of pages it works on, the popup, options page and shortcuts, what it stores and whether it syncs, any account or server it talks to, how updates are released and what broke before. Screenshots of each screen and of its work on a page, a feature list or the store description: up to 5 files as images, Word, Excel or PDF. Never send store account access or users' data.
We will ask you:
- What does the extension do?
- Which browsers?
- Which sites or pages?
- What has broken before?
Compare packages
| Packages | Basic25 cases for one feature$13 | Standard60 cases, up to 4 features$30 | Premium120 cases, up to 8 features$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 | Browser extension | Browser extension | Browser extension |
| 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 extension?
No. We write the cases and checklists; you or your people run them. We never install or use your extension.
The sites we work on change often. What then?
The cases describe what to look for rather than exact page layouts, and the regression checklist in Premium is meant to be rerun after a site changes.
Will the cases help pass store review?
They check how the extension works, which helps, but each store reviews by its own rules, and we cannot promise approval.
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
DevelopmentEditor test cases
Test cases for a desktop editor: files, editing tools, undo, formats, autosave, settings and updates
Pricefrom $13
DevelopmentAdmin panel test cases
Test cases for an internal admin tool: roles, records, bulk actions, imports, exports and the action log
Pricefrom $13
DevelopmentPricefrom $15