Testing doubles - Revision history

Root at 16:30, 22 October 2025

2025-10-22T16:30:07Z

← Older revision		Revision as of 17:30, 22 October 2025
Line 1:		Line 1:
	Test doubles are substitutes for components in software testing, used to isolate a unit of code from its dependencies to achieve controlled and deterministic test conditions. They emulate the behavior of real components, ensuring the test focuses only on the unit under examination. The term ~~"~~test double~~"~~ encompasses various specific types:		Test doubles are substitutes for components in software testing, used to isolate a unit of code from its dependencies to achieve controlled and deterministic test conditions. They emulate the behavior of real components, ensuring the test focuses only on the unit under examination. The term "test double" encompasses various specific types:

	<span id="dummy"></span>		<span id="dummy"></span>
Line 6:		Line 6:
	Implementation or replica of another object for having an entity of the same type as the original. It doesn't have any logic and their methods return null. They are usually used to fill functions' parameters list and are never actually used.		Implementation or replica of another object for having an entity of the same type as the original. It doesn't have any logic and their methods return null. They are usually used to fill functions' parameters list and are never actually used.

	<syntaxhighlight>ValidateAuthDummy { authorize($user) { return null; } }</syntaxhighlight>		<syntaxhighlight lang="php">ValidateAuthDummy { authorize($user) { return null; } }</syntaxhighlight>
	<span id="stub"></span>		<span id="stub"></span>
	== Stub ==		== Stub ==
Line 12:		Line 12:
	Similar to dummy, but in this case methods return a value that is interesting for us. They are useful for those occasions that we already have something validated but we need to make a bypass of that validation.		Similar to dummy, but in this case methods return a value that is interesting for us. They are useful for those occasions that we already have something validated but we need to make a bypass of that validation.

	<syntaxhighlight>ValidateAuthStub { authorize($user) { return true; } }</syntaxhighlight>		<syntaxhighlight lang="php">ValidateAuthStub { authorize($user) { return true; } }</syntaxhighlight>
	<span id="spies"></span>		<span id="spies"></span>
	== Spies ==		== Spies ==
Line 23:		Line 23:
	It is a clone of an existing object. In it you predefine some values. It will be use to check the logic of a service, due to we already know what should be returned.		It is a clone of an existing object. In it you predefine some values. It will be use to check the logic of a service, due to we already know what should be returned.

	<syntaxhighlight>is_user_authorized() {		<syntaxhighlight lang="php">is_user_authorized() {
	$mockUser = new User().grantAuthorization();		$mockUser = new User().grantAuthorization();
	assert(true, isUserAuthorized($mockUser));		assert(true, isUserAuthorized($mockUser));
Line 34:		Line 34:
	Simulate the complete behaviour of an object with invented data. It can contain predefined logic to simulate the behaviour of the replicated object.		Simulate the complete behaviour of an object with invented data. It can contain predefined logic to simulate the behaviour of the replicated object.

	<syntaxhighlight>ValidateAuthStub {		<syntaxhighlight lang="php">ValidateAuthStub {
	authorize($user) {		authorize($user) {
	return $user == ‘Bob’;		return $user == ‘Bob’;
	}		}
	}</syntaxhighlight>		}</syntaxhighlight>
	~~<!-- From bodyContent 1542994.mraw -->~~

	[[Category:IT backend architecture]]		[[Category:IT backend architecture]]

Maintenance script: Added category IT backend architecture

2025-10-19T17:51:18Z

Added category IT backend architecture

← Older revision		Revision as of 18:51, 19 October 2025
Line 41:		Line 41:
	<!-- From bodyContent 1542994.mraw -->		<!-- From bodyContent 1542994.mraw -->

			[[Category:IT backend architecture]]

Maintenance script: Maintenance script moved page UserDocumentation:Knowledge Central/KC IT/IT backend team/IT backend policies/IT backend architecture/testing doubles to Testing doubles: Cleaned title and categorized

2025-10-19T17:51:17Z

Maintenance script moved page UserDocumentation:Knowledge Central/KC IT/IT backend team/IT backend policies/IT backend architecture/testing doubles to Testing doubles: Cleaned title and categorized

← Older revision	Revision as of 18:51, 19 October 2025
(No difference)

imported>Unknown user at 10:33, 19 April 2025

2025-04-19T10:33:56Z

← Older revision		Revision as of 11:33, 19 April 2025
Line 1:		Line 1:
			Test doubles are substitutes for components in software testing, used to isolate a unit of code from its dependencies to achieve controlled and deterministic test conditions. They emulate the behavior of real components, ensuring the test focuses only on the unit under examination. The term "test double" encompasses various specific types:

			<span id="dummy"></span>
			== Dummy ==

			Implementation or replica of another object for having an entity of the same type as the original. It doesn't have any logic and their methods return null. They are usually used to fill functions' parameters list and are never actually used.

			<syntaxhighlight>ValidateAuthDummy { authorize($user) { return null; } }</syntaxhighlight>
			<span id="stub"></span>
			== Stub ==

			Similar to dummy, but in this case methods return a value that is interesting for us. They are useful for those occasions that we already have something validated but we need to make a bypass of that validation.

			<syntaxhighlight>ValidateAuthStub { authorize($user) { return true; } }</syntaxhighlight>
			<span id="spies"></span>
			== Spies ==

			Are stubs that also record and log some information based on how they were called.

			<span id="mock"></span>
			== Mock ==

			It is a clone of an existing object. In it you predefine some values. It will be use to check the logic of a service, due to we already know what should be returned.

			<syntaxhighlight>is_user_authorized() {
			$mockUser = new User().grantAuthorization();
			assert(true, isUserAuthorized($mockUser));
			}</syntaxhighlight>
			They are specially abused because it's very easy to misuse them by writing tests to simply assert the specific details of the workings of some code rather that its interactions with collaborators. If implementation changes, the test breaks.

			<span id="fake"></span>
			== Fake ==

			Simulate the complete behaviour of an object with invented data. It can contain predefined logic to simulate the behaviour of the replicated object.

			<syntaxhighlight>ValidateAuthStub {
			authorize($user) {
			return $user == ‘Bob’;
			}
			}</syntaxhighlight>
	<!-- From bodyContent 1542994.mraw -->		<!-- From bodyContent 1542994.mraw -->

imported>Unknown user at 10:33, 19 April 2025

2025-04-19T10:33:56Z

← Older revision	Revision as of 11:33, 19 April 2025
(No difference)

imported>Unknown user at 10:33, 19 April 2025

2025-04-19T10:33:56Z

New page