The Vocabulary of Software Testing Is Broken—Here’s a Better One

A Better Vocabulary for Testing

The Vocabulary of Software Testing Is Broken—Here’s a Better One

Alperen Keles argues that terms like "unit test" and "integration test" are too vague to be useful. He proposes five orthogonal categories—scope, purpose, oracle, method, and resource—to describe any test precisely. This framework lets teams upgrade or downgrade tests based on available resources and provides a recipe for choosing the right test given a situation. The article is biased toward random testing but offers a practical, actionable vocabulary for testers.

Contemporary vocabulary for talking about software testing has bothered me for a long time. The concept of a unit in unit test is not really defined, integration tests are integrating arbitrarily scoped modules, the concept of an E2E test makes sense, but it very much underspecifies the actually tested behavior as well as methods for testing it.
  1. jph

    There's low-hanging fruit IMHO by testing using semantic naming vocabulary with semantic error vocabulary.

    Example macro: assert_approx_eq_with_relative_error!(a, b, err). It's a semantic name that explains more about what it does, and the macro also provides a test failure message that guides the developer, or an AI, toward fixes and documentation.

    I wrote the Rust crate Assertables to help with this. See https://crates.io/crates/assertables.

    What I learned is writing semantic testing can help many more kinds of higher-value testing. As a specific example described by the article, I use enumeration testing for proving the UK National Health Service Number validator in Rust is accurate i.e. the test literally checks every number, then I can write tests such as assert_valid_nhs_number("111 111 1111").

  2. ozim

    I would like "non-functional testing" to be called "cross-functional testing".

  3. FabCH

    I find that the biggest problem with all these classifications is that at the end of the day, developers will write whatever works for them in the moment, and not care if it fits your theoretical box.

    I did a paper on it once, to see what tests devs actually write: https://ieeexplore.ieee.org/document/11081450

More from this day

2026-11-22