Eristub

Eristub is a term used in software development to describe a small, replaceable component that acts as a test double for a real service or subsystem during development and testing. It is designed to be easily configured, deterministic, and isolated from the rest of the system, so that tests can run reliably without depending on external resources.

Origin and etymology of eristub are not standardized; the term appears in practitioner discourse and online forums without a formal definition. It is commonly described as a portmanteau or as a contraction related to "stub" with an added modifier to signal resilience or extensibility.

Key characteristics include a minimal interface, predictable behavior, and a pluggable replacement for a real component. An eristub supports easy reconfiguration and, in many cases, records interactions for verification, enabling consistent test outcomes across runs.

Implementation patterns for eristubs vary. Common approaches include hard-coded responses, data-driven configurations, or adapters that simulate real-time behavior. The goal is to provide a stable, controllable stand-in that covers important interaction scenarios while remaining lightweight.

Typical use cases involve unit and integration testing in modular architectures, as well as service virtualization within CI pipelines. For example, in an e-commerce workflow, an eristub for a payment gateway can return pre-defined success or failure responses, allowing the checkout process to be tested in isolation from the real payment service.

Relation to other test doubles is that eristubs are similar to stubs, mocks, and fakes but emphasize stable substitution and easy switching to the real component with minimal changes. Limitations include the risk of masking integration issues if the eristub drifts from the real service. See also: stub, mock, fake, test double, service virtualization.