Characterization testing
A testing technique that records and checks existing software’s observable behavior, including behavior that may be undocumented or unspecified.
Build High Value Software Systems
A characterization test records and verifies the observed behavior of existing software, including behavior that may be undocumented.
- How it is used
- Uses observed-behavior tests to make changes to legacy code safer.
- How deep it goes
- Captures typical paths, edge cases, thresholds, and complex outputs without redefining intended behavior.
- Examples
- Demonstrates discount calculations with negative inputs, invalid types, and differing VIP thresholds.
- What you can do after
- Apply characterization tests to preserve observed behavior while restructuring legacy code.
Read how Build High Value Software Systems explains characterization testing →
Vibe Engineering
A testing technique that records existing software behavior and checks that later changes preserve it except for explicitly intended differences.
- How it is used
- Protects behavioral stability before accepting changes, especially AI-generated modifications with unknown collateral effects.
- How deep it goes
- Defines corpus capture, snapshot comparison, and allowed exceptions, but stops short of proving implementation correctness.
- Examples
- Uses production inputs, edge cases, historical regressions, and markup-parser snapshots with explicitly allowed output changes.
- What you can do after
- Diagnose unexpected behavior changes by comparing pre-change and post-change outputs across a representative corpus.
Read how Vibe Engineering explains characterization testing →
Also covered in
What to know first
- legacy codeLegacy code is existing software code carried forward from earlier development for maintenance or change, regardless of its test coverage or current usefulness.
Related concepts
- software testingkind of · Software testing is the systematic evaluation of software under specified inputs or conditions to assess its behavior against expected results or requirements and identify defects.
- snapshot comparisonimplemented by · Snapshot comparison is a technique that compares a current output or state with a previously recorded representation to identify differences.
- legacy codemeasures · Legacy code is existing software code carried forward from earlier development for maintenance or change, regardless of its test coverage or current usefulness.
- refactoringused by · Refactoring is the disciplined restructuring of existing software to improve its internal qualities while preserving its externally observable behavior.
- code coverageused by · Code coverage is a measure of which portions or behaviors of a program are exercised during testing.
Questions about characterization testing
What is characterization testing?
A testing technique that records and checks existing software’s observable behavior, including behavior that may be undocumented or unspecified.
Which Manning books explain characterization testing?
Build High Value Software Systems and Vibe Engineering.
What should I know before learning characterization testing?
Manning books that teach characterization testing usually introduce legacy code first.
What is characterization testing a kind of?
Characterization testing is a kind of software testing. Software testing is the systematic evaluation of software under specified inputs or conditions to assess its behavior against expected results or requirements and identify defects.
What is characterization testing also called?
Characterization testing is also called characterization test.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

