Manual testing before every release.
Test cases, regression, checks on real iPhones and Android phones. A QA engineer works in your tracker and finds bugs before your customers do.
Website testing at Tochno is manual checking of a website or store by a live QA engineer before every release: following test cases, on real iPhones and Android phones, with bug reports and a go / no-go decision. It suits teams without their own QA. The cost starts from $20 per hour, a one-off regression from UAH 4,000, and the first day is a trial.
When you need a QA engineer
Testing you can repeat
We record everything in test cases, so the next regression takes hours, not days.
One-off or ongoing
- Checklist or test cases
- Bug reports with video
- Go / no-go decision
- Test cases and their upkeep
- Regression before every release
- Work in your tracker
- Weekly report
What a release report looks like
Instead of "we tested it, looks fine", you get a clear decision: ship or not, and what exactly is blocking it.
How we join your team
- day 1OnboardingAccess, tracker, product overview.
- days 2–3Test casesWe document the key scenarios.
- releaseRegressionRunning the cases, bug reports.
- weeklyReportQuality metrics and risks.
What manual testing includes
Manual testing is ongoing work with your product, not a one-off check. A QA engineer connects to your tracker, describes the key scenarios in test cases and runs them before every release.
What you get in practice:
- test cases and checklists that are updated after every release;
- functional and regression testing, plus a smoke check after deployment;
- cross-browser and mobile checks: Safari, Chrome, Firefox, Edge, iPhone 12–15, Samsung, Xiaomi, Pixel;
- bug reports with video, reproduction steps and a priority based on impact on customers;
- a release report with a clear decision: ship or not.
This service works best when developers test their own work and miss the obvious, when most customers come from phones, or when you need to independently accept a contractor's work before paying.
We complement real devices with BrowserStack only for rare combinations. That way you see what the customer sees, not what an emulator shows.
How the work goes
The start usually takes two business days. On day one we get access and get to know the product and the tracker. Over the next two days we describe the most important scenarios: login, search, cart, payment, forms.
After that every release goes through the same cycle: regression against the cases, bug reports, re-checking after fixes, a short report. Every week you get a summary: what was found, what was fixed, which risks remain.
If you are not sure you need this, start with a trial day. You pay only if we continue.
How much does website testing cost and what affects the price
Website testing starts from $20 per hour. A one-off regression against a checklist starts from UAH 4,000, and monthly QA from $800. The total depends on the size of the product and the release frequency.
| Factor | How it affects the price |
|---|---|
| Number of scenarios | More cases mean a longer first regression, but repeat runs are cheaper |
| Release frequency | Weekly releases are cheaper to cover with a monthly package than hourly |
| Devices and browsers | A wider matrix means more hours of cross-browser checks |
| Integration complexity | Payment, delivery and CRM need separate cases |
| Documentation | Ready requirements shorten the time to learn the product |
Hourly billing suits one-off tasks: the minimum order is one day, i.e. 8 hours. Current rates by role are on the pricing page. We give an exact estimate after the brief, usually within one business day.
Manual testing or an e-commerce QA audit
These are two different services. Manual testing is ongoing work with every release of your website or app. If you need a one-off deep check of an online store against a checklist of 150+ points, choose an e-commerce QA audit: from UAH 6,000 in 3–5 days. It is cheaper to start with and gives a full picture of the problems before you launch ads.
The two formats are often combined: first an audit, then regular testing for every release.
When manual testing is not the right fit
Manual testing is not always the best choice. Here are a few situations and better alternatives:
- The same scenarios repeat every week and manual regression eats many hours. In that case test automation on Playwright is better. We break down the difference in the article manual vs automated testing.
- The bugs seem to live in the code itself: slow queries, weak architecture. You then need a code audit.
- The site is simple and you only want a quick sense of whether there are obvious problems. Start with a free 48-hour express check.
What makes testing at Tochno different
We do not stop at "everything works". Every bug comes with a video, steps and a priority that reflects impact on customers, not abstract severity. An example of such a report and a test case is in the article how we test: a bug report and a test case.
We work in your tracker: Jira, Linear, Trello, ClickUp, YouTrack. After fixes we re-check. And at the end of every release you get not a guess but a go / no-go decision with a list of what blocks the launch.
If you need ongoing support alongside development, see also website support with QA.
If you want to scope the work in advance, send a link to your website or app, and we will suggest where to start.
How is this different from a QA audit?
An audit is a one-off deep check. Manual testing is ongoing work with every release.
Do you work in our tracker?
Yes: Jira, Linear, Trello, ClickUp, YouTrack.
What devices do you have?
Real iPhones and Android phones, plus BrowserStack for rare combinations.
Can we start with a trial?
Yes, the first day is a trial and you pay only if we continue.
How much does website testing cost?
Website testing starts from $20 per hour, a one-off regression against a checklist from UAH 4,000, and monthly QA from $800. The final amount depends on the number of scenarios, release frequency and the breadth of the device matrix. We give an estimate after the brief.
How long does manual testing take?
The start takes about two business days: access, getting to know the product and the first test cases. The first day can be used as a trial. A single regression before a release usually takes from a few hours to one day, depending on the number of scenarios and devices.
How does manual testing differ from automated testing?
Manual testing is done by a person and is flexible: it catches UX problems, unusual scenarios and new features that have no tests yet. Automated tests quickly repeat stable scenarios. For most small projects it is better to start with manual QA and add automated tests later.
What do I need to provide to start testing?
A link to the website or app, access to a test environment and to your tracker (Jira, Linear, Trello or another), and a short description of the key scenarios. If you have no documentation, that is fine: we will write the test cases ourselves in the first two or three days.
Tell us about your product.
We reply within 2 business hours. An estimate with a price and timeline range follows within 1 day.