Test name

Q: How deeply does Unit Testing Principles, Practices, and Patterns cover test name?

Contrasts rigid and plain-English conventions and refactors concrete names, but stops short of a complete naming standard.

As explained in Unit Testing Principles, Practices, and Patterns

A test name is the human-readable identifier assigned to an automated test to indicate the behavior it verifies.

A test name is a human-readable identifier that states the behavior an automated test verifies. Expressive names clarify both the expected behavior and its connection to business requirements. section 3.4

Prefer short phrases in plain English over rigid MethodUnderTest_Scenario_ExpectedResult names. Rigid templates emphasize implementation details, repeat method names, and impose a cognitive tax on readers. section 3.4

Refactoring a delivery test name

Replace IsDeliveryValid_InvalidDate_ReturnsFalse with Delivery_with_a_past_date_is_invalid. The revised name communicates the domain behavior directly without explaining where a result is returned.

How Unit Testing Principles, Practices, and Patterns covers it

Cover of Unit Testing Principles, Practices, and Patterns

liveBook manning.com

Read Unit Testing Principles, Practices, and Patterns on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

The Art of Unit Testing 3eThe textual name assigned to a test to communicate the tested unit, scenario, and expected behavior or exit point.

Compare how 2 books explain test name →

Related concepts

testconfigures · A test is a procedure or check that evaluates behavior using specified inputs or evidence against expected results or criteria.
behaviorpart of · Behavior is the externally observable actions, responses, outputs, or effects of a system or object under specified conditions or interactions.
scenariopart of · A scenario is a concrete description of a situation or conditions, often including actions and expected or possible outcomes, for analysis or evaluation.
naming standardconfigured by · A naming standard is an established set of rules or patterns for assigning names consistently to software elements, resources, or other artifacts.
deployment pipelineused by · A sequence of automated or manual stages that builds, tests or validates, packages, and delivers software or models toward deployment.
implementation detailcontrasts with · An implementation detail is an internal design choice, representation, or mechanism that is not part of a software component’s externally observable behavior or contract.

This explainer was generated by Manning's knowledge graph from the text of Unit Testing Principles, Practices, and Patterns. The section links point to the parts of the book it draws on.