Perne
Testing: manual and automated tests: illustration 1
Websites

Testing: manual and automated tests

We run manual testing by scenario: sign-up, payment, forms, the user account area, the mobile version and different browsers. We write test cases and log the bugs we find with steps to reproduce, screenshots and priority. For repeated checks we build automated tests with Playwright or Cypress for the interface and pytest or Jest for the API. We connect the tests to GitHub Actions or GitLab CI, so they run on every code change. Testing does not replace your development team; it helps them see problems faster.

from 30,000 ₸ (≈ $60) one-off

timeline: 3–10 working days

  • Studying the product and a list of key scenarios agreed with you
  • Manual testing on desktop and mobile, in Chrome, Firefox and Safari where the environment is available
  • Test cases and a report with found bugs, priorities and steps to reproduce

Order

Message on WhatsApp
TelegramCall

The service name is added to the message for you.

This is a starting price; we give the final amount before work starts. USD is approximate.

What is included

  • Studying the product and a list of key scenarios agreed with you
  • Manual testing on desktop and mobile, in Chrome, Firefox and Safari where the environment is available
  • Test cases and a report with found bugs, priorities and steps to reproduce
  • Automated tests with Playwright or Cypress for 5-10 key scenarios
  • API checks with pytest or Jest if the project has an API
  • Connecting the tests to GitHub Actions or GitLab CI
  • A short guide on how to run the tests and add new ones

Who it is for

For companies that ship a website or app and want fewer bugs after release, and for teams without a dedicated tester. It is not a fit if you only need the found bugs fixed without any checks; in that case, order the bug-fixing service. Testing does not guarantee that the product will have no bugs.

Not included

To avoid surprises, here is what the base price does not cover and what is discussed separately:

  • Fixing the bugs found in the code: done by your team or by the separate bug-fixing service
  • Load and security testing: separate work with other tools
  • Testing on a large fleet of real devices, if they are not in the agreed list
  • A guarantee of no bugs after release

How the work goes

  1. 1

    Discovery call

    We talk through your business, your customers and what the site has to do. Everything is online: a video call, WhatsApp or Telegram.

  2. 2

    Structure and price

    We agree the list of pages and features, the price and the timeline in a written agreement. 50% is paid upfront.

  3. 3

    Design and build

    We build the site in parts and share a preview link, so changes are easy to make while the work is in progress.

  4. 4

    Launch and handover

    We publish the site, connect your domain and show you how to edit texts and prices. The remaining 50% is paid after delivery.

FAQ

Test cases, automated tests, reports and guides are handed over to you and become part of your project. If the tests use third-party libraries, we list their licences. The test code lives in your repository, and you can keep using it without us.

The price includes two rounds of revisions to the report and tests after the first version: clarifying scenarios, adding missing checks and corrections to the guide. Extending the list of scenarios beyond the agreed one is estimated separately.

Usually 3 to 10 working days depending on the size of the product and the number of scenarios. Automated tests take longer than manual checks, because they must be set up for your test environment. We will name the exact timing after studying the product.

Access to a test environment with test accounts, a description of the business logic and user roles, and the list of the most important features. If you want automated tests, we need access to the repository and the CI system, plus someone who can explain the environment.

Yes, tests, especially automated ones, must not create real orders or charge money. We work on a test environment or in the payment provider's sandbox. If no such environment exists, we first suggest preparing one, because the risk of damaging data is too high otherwise.

Each bug is described with steps to reproduce, the expected and actual result, a screenshot or video, and a priority. The report can live in Jira, YouTrack, Trello or a spreadsheet, whichever suits your team. We discuss duplicates and disputed cases with you before passing them to developers.

You may also need

Website bug fixing

Website bug fixing

We find what broke your site and fix it: a form, a layout, slow loading or an error after an update.

from 3,000 ₸ (≈ $6) one-off

Timeline: timeline: 1–2 working days

Custom backend and API development

Custom backend and API development

A server side and API for your website, app or integrations: data, authorisation and documentation.

from 80,000 ₸ (≈ $160) one-off

Timeline: timeline: 10–25 working days

Shall we discuss your project?

The product name and a link to this page are filled into the WhatsApp message for you.

Message on WhatsApp
TelegramCall

Or send a request

We will reply in the channel you choose: WhatsApp, Telegram, phone or email. Your contact is used only to reply.

Service
How to reply

from 30,000 ₸ (≈ $60) one-off

Message on WhatsAppTelegramCall