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
Technical specification: booking website for a yoga studio
1. Project goals
- Let clients see the timetable and book a class in under one minute, from a phone.
- Sell class passes and memberships online.
- Cut the time staff spend on bookings from about 10 hours a week to under 2.
Success measures (3 months after launch): 70% of bookings made online; no-shows below 10%.
2. Users
| Role | What they need |
|---|---|
| Visitor | See classes, prices and teachers; buy a first-class trial |
| Client | Book and cancel classes, see remaining passes, join a waitlist |
| Teacher | See their own classes and the list of booked clients |
| Admin | Manage timetable, prices, passes, teachers and refunds |
3. Pages and screens
- Home: next classes today, trial offer, studio address.
- Timetable: week view, filters by class type, level, teacher and room.
- Class page: description, teacher, length, places left, Book button.
- Prices: single class, 5- and 10-class passes, monthly membership.
- Teachers: list and individual profiles.
- Account: upcoming bookings, history, passes, payment methods.
- Admin panel: timetable editor, client list, sales report.
4. Key features
4.1 Booking
- A client can book if they have a valid pass or pay for a single class.
- Class capacity is set per room (Room A: 18, Room B: 10).
- When a class is full, the client can join a waitlist; if a place opens, the first person in line gets it and receives an email and text message.
4.2 Cancellation
- Free cancellation up to 12 hours before class; the pass credit returns.
- Later cancellation or a no-show uses up the credit.
4.3 Payments
- Card payments through a payment provider chosen by the studio.
- Passes expire: 5-class after 2 months, 10-class after 3 months.
4.4 Notifications
- Booking confirmation, reminder 3 hours before class, waitlist updates.
5. Non-functional requirements
- Mobile-first; pages load in under 2 seconds on 4G.
- Works in the two latest versions of major browsers.
- Personal data stored in line with local data protection law.
6. Open questions
| # | Question | Who decides |
|---|---|---|
| 1 | Do teachers mark attendance in the app, or does the front desk? | Studio owner |
| 2 | Is a 2-week trial pass needed in addition to a single trial class? | Studio owner |
| 3 | Should the timetable be embedded on the current website or replace it? | Owner + developer |
| 4 | Which payment provider and text-message service are preferred? | Owner |
Client: Lotus Lane Yoga, a studio with 2 rooms, 9 teachers and about 60 classes a week. Today bookings go through direct messages and a paper sign-up sheet. Standard package: specification up to 10 pages. Excerpt below.
The client and all details are made up.
About this service
Releases break in boring places: the checkout on a small iPhone, a form that accepts an empty email, a password reset link that expires too soon. We write test cases for your website or app from its description, screens or user flows: steps, test data and the expected result for each, grouped into a smoke test, regression checks and edge cases. Anyone on your team can run the checklist before release and report bugs in a consistent way.
What is included
- What you getTest cases with ID, steps, test data and expected result, grouped by feature and priority, a pre-release checklist and a bug report template, as formatted text you can paste into a spreadsheet or test management tool.
- Smoke testThe few checks that must pass every time
- Feature test casesSteps, data and expected result
- Edge casesEmpty fields, long text, bad network, wrong input
- Device coverageWhich checks to repeat on which browsers
- Bug report templateSo every bug arrives with the same details
How it works
- 1BriefYou share screens, flows and devices
- 2WritingWe write cases by feature and priority
- 3ChecklistYou get cases ready to run
What we need from you
Links to the site or app if public, screenshots or a description of the screens and flows, the devices and browsers your users have, and what changed in this release.
We will ask you:
- Is it a website, a web app or a mobile app?
- Which features or flows must be tested?
- Which devices and browsers matter most?
- Who will run the tests?
Compare packages
| Packages | BasicUp to 30 test cases$15 | StandardUp to 80 test cases$35 | PremiumUp to 200 test cases$69 |
|---|---|---|---|
| Deadline | 1 day | 3 days | 5 days |
| Revisions | 1 | 2 | 3 |
| Test cases | up to 30 | up to 80 | up to 200 |
| Device and browser sets | 1 | up to 3 | up to 6 |
| Bug report template | Yes | Yes | Yes |
| 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 the site yourselves?
No. We write the test cases and checklist; your team or a tester runs them and records the results.
Can I import them into TestRail or Qase?
Yes. Ask for a CSV-style table in the brief, and the columns will match a typical import.
Do you write test code, such as Playwright or Selenium scripts?
No, these are manual test cases. They are often the first step before a team writes test code.