DevelopmentSaaS test cases
Test cases for a SaaS dashboard: roles, permissions, data tables, filters, billing and settings
Pricefrom $13
Booking 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
Booking sites break at the edges of time: two people taking the last slot at once, a booking across a time zone or a clock change, a cancellation just inside the free window. We write test cases for the flow you describe: search and dates, free slots, the booking form, deposits or full payment, confirmations and reminders, changes and cancellations, and the admin side where slots and schedules are set. Each case has steps, test data such as a date on the edge of your rules, the expected result and a priority. Send screenshots or a link and your rules for slots, breaks, deposits and refunds. You get an Excel workbook with cases and checklists; from Standard a test plan in Word, and in Premium a regression checklist and a bug report template. We write the cases; you run them. We never make real bookings or open your system.
What is included
- What you getAn Excel workbook with the booking cases: ID, area, title, preconditions, steps, test data such as a slot right before closing time, expected result, priority and a column for your result, plus a checklist per area. From Standard, a Word test plan with devices, browsers and time zones; in Premium, a full plan, a regression checklist to repeat after schedule or price changes and a bug report template.
- Slots and calendarFree, taken, break and closed times
- Double bookingsTwo people on the last slot at once
- Time zones and datesClock changes, holidays and dates far ahead
- Deposits and refundsAs your rules say, in test mode
- Changes and cancellationsInside and outside your free window
How it works
- 1RulesYou send the screens and your booking 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 runYou or your people run the cases and note the results
What we need from you
What is booked (rooms, tables, appointments, tours, rentals), the platform or booking widget, the steps from search to confirmation, your rules for slot length, breaks, opening hours, minimum notice, deposits, changes, cancellations and refunds, the time zones you serve, how confirmations and reminders are sent, the roles on the admin side and what broke before. Screenshots of each step: up to 5 files as images, Word, Excel or PDF. Never send passwords or real guest data.
We will ask you:
- What do people book?
- What are your rules for slots and cancellations?
- Do you take payment when booking?
- Which time zones and languages?
- What has broken before?
Compare packages
| Packages | Basic25 cases for one booking step$13 | Standard60 cases, up to 4 areas$31 | Premium120 cases, up to 8 areas$61 |
|---|---|---|---|
| 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 | Booking website | Booking website | Booking website |
| 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 booking site?
No. We write the cases and checklists; you or your people run them. We never make bookings, pay or log in to your system.
Can you cover payments and refunds?
Yes, as cases run in your payment provider's test mode with its test cards, following your deposit and refund rules. Never run them with real cards.
Our booking runs on a third-party widget. Can you cover it?
Yes, as far as your site shows it: the cases check what a guest sees and what reaches you. How the widget works inside is up to its provider.
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
DevelopmentSign-up and login cases
Test cases for sign-up and login: email and SMS codes, passwords, social login, reset and sessions
Pricefrom $13
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