Software testing — manual and automated

Software testing checks a website or app through a user's eyes: sign-up, cart, payment, different browsers and phones. Before a release or after a bad update, describe the product in an order, and testers will send responses. Or pick a specialist yourself by services, portfolio and client reviews.

Looking right now

fresh orders

Software testers

How much website or app testing costs

What affects the price

  • Scope of features and flows

    A landing page with a contact form and an app with user accounts, roles and payments have very different numbers of scenarios to walk through.

  • Browsers, devices and OS versions

    Every extra browser, phone model or Android and iOS version means one more run of the same checks.

  • Manual checks or automated tests

    Automated tests first have to be written and set up, then maintained, but after every update they rerun the same checks with no manual work.

  • Requirements and test cases

    If there are no written requirements or test cases, the tester first has to learn the product and write them — a separate stage.

  • One release or ongoing work

    Testing a single release is often priced as a project, while testing every update over months is paid hourly or monthly.

Prices come from specialists' profiles on Nexperity and update automatically. You agree the final price with the specialist directly.

How to find a QA tester

Two ways — pick the one that suits you

Pick a specialist yourself

Compare portfolios, prices and reviews, and send a request to the one who suits you.
  1. 1Open specialists' profiles and their work
  2. 2Send a request that describes the task
  3. 3Once accepted — contact the specialist directly

Post an order

Describe the task once, and specialists will send you their responses.
  1. 1Describe the task, payment and the timing you want
  2. 2Receive responses from specialists
  3. 3Pick the best specialist and agree directly

How to choose a software tester

  1. 1

    A sample bug report

    Ask to see a bug report or test cases from a similar project, without the client's data: with a good bug description, a developer sees right away how to reproduce the bug.

  2. 2

    Your type of product

    A website, a mobile app, an API and a game need different tools, and each has its own typical bugs. Look for a tester whose services include your platform.

  3. 3

    Real devices, not just an emulator

    For a mobile app, ask which phones and OS versions will be used for testing: some bugs only show up on a real device.

  4. 4

    A test environment and accounts

    Agree on where the testing will be done: load tests or real payments on the live site can affect your customers. Give the tester separate test accounts, not your own.

  5. 5

    What you get at the end

    Agree on the result: a report on the bugs found, test cases or automated tests in the repository. Also check whether a retest after fixes is included.

What to put in the order

The more precise the description, the more precise the prices in responses.
  • What to test: a website, mobile app, API or game — and what stage the product is at

  • Key flows: sign-up, search, cart, payment, user account

  • Browsers, platforms and devices the product must be checked on

  • What you need: manual testing, test cases, automated tests or load testing

  • Whether there is a separate test environment or the checks have to run on the live site

  • Payment, the release date and whether future updates need testing too

Questions about Nexperity

How Nexperity works — separately for clients and for specialists

For clients

Nothing. Searching for specialists, sending requests, posting orders and receiving responses are free.

For specialists

Nothing for now: this is the free period, and no subscription is needed yet. Nexperity takes no commission on deals — you settle with the client directly.

Related categories

Are you a software tester?

Get orders from your category and respond to them — with no commission on deals.