Atest doubleissoftware used in softwaretest automation that satisfies a dependency so that the test need not depend on production code. A test double provides functionality via an interface that the software under test cannot distinguish from production code.
Aprogrammer generally uses a test double to isolate the behavior of the consuming code from the rest of the codebase.
A test double is usually a simplified version of the production code and may include capabilities specific to testing.
A test double may be used to simplify and speed test execution.
For example, a program that uses a databaseserver is relatively slow and consumes significant system resources – which impedes testing productivity. Also, a test case might require values outside those stored in the database.
A test double might provide a static value instead of accessing a database.
A test double may be used to test part of the system that is ready for testing even if its dependencies are not.
For example, in a system with modules Login, Home and User, suppose Login is ready for test, but the other two are not.
The consumed functions of Home and User can be implemented as test doubles so that Login can be tested.
Mock — verifies output via expectations defined before the test runs (differs from Mock object)
Spy — supports setting the output of a call before a test runs and verifying input parameters after the test runs
Fake — a relatively full-function implementation that is better suited to testing than the production version; e.g. an in-memory database instead of a database server
Dummy value — a value that is required for the tested interface but for which the test case does not depend
While there is no open standard for categories, Martin Fowler used these terms in his article, Mocks Aren't Stubs[2] referring to Meszaros' book. Microsoft also used the same terms and definitions in an article titled, Exploring The Continuum Of Test Doubles.[3]
Averified fake is a fake object whose behavior has been verified to match that of the real object using a set of tests that run against both the verified fake and the real implementation.[9]
^Byars, Brandon. "Testing Microservices with Mountebank", Manning Publications, MEAP began March 2017. ISBN9781617294778. Retrieved on 07 December 2017.
