# Software Testing

> Checking that code does what it should, before real people use it.

**Field:** Software Development  
**Category:** Testing & Quality  
**Also known as:** Testing, Code Testing, QA Testing

## Think of it like

Think of it like tasting soup before you serve it. You check it is right first.

## Definition

Software testing is checking that code does what it should before people use it. A test runs part of the program with a known input. Then it checks the output against the answer you expect. Most tests are small programs that run in seconds, again and again. When a test fails, you know something broke and roughly where.

## Example

Lucy changes how her shop adds up prices. Her 200 tests run in 4 seconds, and one fails: the discount is now wrong.

## Why it matters

A bug found by a test costs minutes. The same bug found by a customer costs money and trust.

## Common mistake

Testing only the happy path. Most bugs hide in the odd cases, like an empty cart or a negative price.

## Three principles

- **Known input, known answer.** Then compare.
- **Run it often.** Seconds, not hours.
- **A fail points the way.** To what broke.

## Related terms

- [Test Case](https://learn.benibix.com/term/development/test-case)
- [Unit Test](https://learn.benibix.com/term/development/unit-test)
- [Bug](https://learn.benibix.com/term/development/bug)
- [Debugging](https://learn.benibix.com/term/development/debugging)

---

Source: https://learn.benibix.com/term/development/software-testing
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-17
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
