DevelopmentSign-up and login cases
Test cases for sign-up and login: email and SMS codes, passwords, social login, reset and sessions
Pricefrom $13
SaaS test casesWebsite
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
In a SaaS dashboard the costly bugs are rarely on the main screen: a viewer who can still delete a record, a filter that drops rows when combined with a date range, an invite link that still works after the seat is removed, a downgrade that leaves paid features on. We write test cases for the screens and rules you describe: roles and permissions, tables, filters, sorting and paging, forms, exports, notifications, settings, invites and subscription billing. Each case has steps, test data, the expected result and a priority. Send screenshots, a feature list or docs and your roles table if you have one. You get an Excel workbook with cases and checklists; from Standard a Word test plan, and in Premium a regression checklist and a bug report template. We write the cases; your people run them. We never log in to your product.
What is included
- What you getAn Excel workbook with the dashboard cases: ID, area, role, title, preconditions, steps, test data, expected result, priority and a column for your result, plus a checklist per area. From Standard, a Word test plan with roles, browsers and what counts as ready for release; in Premium, a full plan, a regression checklist for every release and a bug report template.
- Roles and permissionsWhat each role can see, edit and delete
- Tables and filtersSorting, combined filters, paging and empty states
- Invites and membersAdding, removing and changing members of a workspace
- Plans and billingUpgrades, downgrades, trials and limits, in test mode
- Exports and settingsCSV files, notifications and account settings
How it works
- 1ProductYou send screens, a feature list and the roles
- 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 before each release
What we need from you
What the product does and who uses it, the screens or features to cover, the roles and what each may do, plan limits and what happens on upgrade, downgrade or the end of a trial, the payment provider if billing is in scope, the browsers you support, the integrations people connect and what broke before. Screenshots, a feature list, docs or requirements help most: up to 5 files as images, Word, Excel or PDF. Never send logins, API keys or real customer data.
We will ask you:
- What does the product do?
- Which roles are there?
- Which areas matter most?
- Which browsers do you support?
- What has broken before?
Compare packages
| Packages | Basic25 cases for one dashboard area$13 | Standard60 cases, up to 4 areas$30 | Premium120 cases, up to 8 areas$62 |
|---|---|---|---|
| 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 | SaaS dashboard | SaaS dashboard | SaaS dashboard |
| 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 product?
No. We write the cases and checklists; your people run them and note the results. We never log in to, use or test your product.
Can the cases cover the API?
If you send API docs, we add cases with requests and expected answers for your developer to run with their own tools. Without docs, the cases follow the screens.
Is this a security check?
The cases include basic access checks, such as a role opening a page it should not. 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.
Can I import the cases into my test tool?
The workbook is in Excel and opens in Google Sheets. Most test management tools import a CSV file, which you save from Excel in one step; you may need to match the column names.
Did not find your answer?
Development
DevelopmentCheckout test cases
Test cases for checkout and payment: totals, taxes, shipping, coupons, cards, failed payments and refunds
Pricefrom $13
DevelopmentCMS site test cases
Test cases for a blog or CMS site: publishing, editor roles, categories, search, comments and updates
Pricefrom $13
DevelopmentForm test cases
Test cases for website forms and leads: field checks, spam protection, delivery to email or CRM and consent
Pricefrom $13