Isolation

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

Distinguishes isolation targets and dependency treatment, then stops short of broader test-design guidance.

As explained in Unit Testing Principles, Practices, and Patterns

The isolation attribute is the aspect of unit testing that specifies what a test or system under test must be isolated from.

Isolation specifies what unit tests or the system under test must be separated from. The London school isolates the system under test from collaborators; the classical school isolates tests from one another. section 2.2

The two interpretations lead to different testing boundaries:

London-style tests treat a class as the unit and replace mutable dependencies, while retaining immutable values. section 2.2
Immutable values such as numbers, enums, and value objects need no test doubles because their contents cannot change. section 2.2

Purchase with isolated inventory

A purchase test substitutes the mutable store with a mock, configures insufficient inventory, asserts failure, and verifies that inventory removal never occurs.

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

Learn Docker in a Month of Lunches, Second EditionIsolation is the separation of applications or execution environments so that one cannot directly interfere with another.
liveBook manning.com

Build an AI Agent (From Scratch)Context isolation is the separation of the information supplied to one agent from the context supplied to another agent during coordinated execution.
liveBook manning.com

Apache Kafka in Actionisolation.level is a Kafka consumer configuration that determines whether records from uncommitted transactions can be read.
liveBook manning.com

LatencyTransaction isolation is the property governing how concurrently executing transactions are protected from one another's intermediate or conflicting effects.
liveBook manning.com

Rust in Action: Systems programming concepts and techniquesIsolation is the separation of program execution or resources so that activity in one environment is restricted from directly affecting another.
liveBook manning.com

Platform Engineering on KubernetesAn isolation level is the degree to which one tenant's resources, operations, and access are separated from those of other tenants.
liveBook manning.com

Build Applications with Local AI Models on a MacThe separation of a project's packages and runtime from those of other projects or the host system.

Compare how 8 books explain isolation →

Related concepts

ACIDpart of · ACID is the set of database transaction properties—atomicity, consistency, isolation, and durability—that characterize reliable transactional behavior.
serializable isolation levelincludes · Serializable isolation is a transaction isolation level that ensures concurrent transactions produce results equivalent to those of some serial execution order.
repeatable read isolation levelincludes · Repeatable read is a database transaction-isolation level that prevents a transaction from observing changes to data it has already read during that transaction.
read committed isolation levelincludes · A database transaction isolation level that prevents reads of uncommitted changes while allowing later reads in a transaction to observe newer committed data.
subagentused by · A subagent is an agent delegated a bounded task by another agent and operating under its coordination or authority.
read uncommittedincludes · Read uncommitted is a transaction isolation level that allows a transaction to read data written by other transactions before those changes are committed.

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.