Software testing: what to know

What the job involves, what changes the price, and what to ask a pro.

What software testing is

A tester checks software for bugs by running scripts and manual checks, documents the issues clearly and verifies the fixes before release. You need it before a launch, after a big change, or when your software keeps failing in ways your team cannot reproduce.

Signs you need it

  • Users report bugs that your team cannot reproduce
  • Each release breaks something that worked before
  • Your software crashes or gives wrong results in certain cases
  • You are about to launch and have not tested the full process
  • A team has changed the code a lot and no one knows what else is affected

What the pro does

  • Reviews the software, its features and the risks that matter most
  • Plans the tests, including manual checks and automated test scripts where useful
  • Runs the tests on the devices, browsers or systems your users use
  • Logs each bug with steps to reproduce, the expected result and the actual result
  • Retests each fix and reports the status of the release

What changes the price

Every job is different, so we do not publish prices. These are the things that move the quote up or down.

  • The size and number of features to test
  • The number of devices, browsers and operating systems
  • Whether automated test scripts must be written or only manual tests run
  • The number of releases and retests needed
  • Whether performance or security testing is included
  • How quickly the test report is needed

What a written quote should spell out

  • The features and devices covered by the test plan
  • Whether automated scripts are written and delivered
  • The bug reports and the retest rounds included
  • The test report at the end and its format
  • Who owns the test scripts and the reports

Questions to ask before you hire

  • Which devices and browsers will you test on?
  • Will the bug reports include steps I can repeat?
  • Do you write automated tests that I can run later?
  • How many retest rounds are included?
  • Who owns the test scripts and the reports?
  • Can you tell me how much of the software is covered?

Red flags

  • Says the software is fully tested without a test plan
  • Will not show example bug reports
  • Writes bug reports that cannot be repeated
  • Keeps the test scripts and reports under its own account

What you can do yourself

List the main things your users do with the software and test each one yourself, writing down any bug with the steps you took and a screenshot. Keep a copy of the version you tested. Hire a tester for a full test plan, the devices you cannot cover and the release check.

Licenses and permits

A license is usually not required for software testing. Check with your state or local licensing agency about any business registration that applies, and ask the tester for its contract terms and examples of its bug reports.

Software testing questions

Can testing find every bug?

No. Testing lowers the risk of bugs reaching users, but no test finds everything. A good plan covers the most important paths first.

Should I test myself or hire a tester?

You can test the basics yourself. A tester is worth it for a launch, many devices or a complex system.

How do I know a bug is fixed?

A tester should retest the exact steps and confirm the result in writing for each bug.

Pro reviewers

Pros who offer software testing remotely can improve this guide, like Wikipedia. We check every edit before it goes live. Every approved edit is credited in the edit history and on the pro's profile.

Edit history

How guide reviews work

How it works

  1. 1. Describe the job

    Pick the service, add your ZIP and a sentence about what is going on.

  2. 2. Pick the pros you want

    See screened pros who serve your ZIP and choose who you want to hear from.

  3. 3. They reach out

    They contact you the way you chose: phone, email or in-app messages.

More web and software development guides

Find a pro near you

Find a pro

About this guide

Request software testing