# Automated Testing

> Tests written as code. A computer runs them on every change.

**Field:** Software Development  
**Category:** Testing & Quality  
**Also known as:** Test Automation, Automated Tests, Automated Software Testing

## Think of it like

Think of it like a robot that checks each door in a house at night. It never gets tired and never skips one.

## Definition

Automated testing means tests written as code that a computer runs for you. Each test sets something up, runs part of the app and checks the result. A whole suite can run in seconds or minutes. It runs the same way every time, on every change. Teams usually run it on each push, in their CI pipeline.

## Example

Lucy's shop has 400 automated tests. They run on every push and finish in two minutes.

## Example code

```console
$ npm test

 Test Files  12 passed (12)
      Tests  400 passed (400)
```

One command runs all the tests and says how many passed.

## Why it matters

People forget checks. A computer runs every check, every time, and catches old bugs coming back.

## Common mistake

Writing tests for things that change each week. Tests that keep breaking soon get ignored.

## Three principles

- **Tests as code.** A computer runs them, not a person.
- **Every change.** Run them on each push.
- **Same every time.** No step is ever skipped.

## Related terms

- [Manual Testing](https://learn.benibix.com/term/development/manual-testing)
- [Test Suite](https://learn.benibix.com/term/development/test-suite)
- [Test Runner](https://learn.benibix.com/term/development/test-runner)
- [Continuous Integration (CI)](https://learn.benibix.com/term/development/continuous-integration)
- [Test Pyramid](https://learn.benibix.com/term/development/test-pyramid)

## Told apart from

- [Manual Testing vs Automated Testing](https://learn.benibix.com/compare/manual-testing-vs-automated-testing): People think automated tests mean nobody has to test by hand, and that is not so. A script repeats the same check the same way, fast, on every change. A person notices what feels wrong, like a confusing page or a button in an odd place. A script only checks what someone wrote down, so most teams keep both.

![A pyramid in three layers. The wide base, lit up, is unit tests: many, fast and cheap. The middle is integration tests: fewer, slower. The narrow top is end-to-end tests: a few, slow and costly. A small cloud above the tip is labelled manual and exploratory testing, done by people. An arrow up the side says slower and costlier toward the top.](https://learn.benibix.com/diagrams/dev3-test-pyramid.svg)

---

Source: https://learn.benibix.com/term/development/automated-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.
