Tests Unitaires - Revision history

Fukakai at 15:35, 25 September 2020

2020-09-25T15:35:32Z

← Older revision		Revision as of 17:35, 25 September 2020
Line 92:		Line 92:
	</source>		</source>
	===@MockBean===		===@MockBean===
			Spring Mock Bean
			=PowerMock=

Fukakai at 15:34, 25 September 2020

2020-09-25T15:34:49Z

@@ Line 13: / Line 13: @@
 =Mockito=
 Mocks vs Stubs = Behavioral testing vs State testing
 ==Stubbing==
 Empty class, only return the expected
@@ Line 29: / Line 31: @@
 ==Spy==
 A Spy is a Stub than is also collecting informations during the test
 ** How many times this method is called ?
 ** Is this method is called at least once ?
@@ Line 60: / Line 65: @@
 @Test(expected=RuntimeException.class)
 </source>

Fukakai at 15:21, 25 September 2020

2020-09-25T15:21:08Z

@@ Line 1: / Line 1: @@
 =Before & After=
 ===@Before @After===
@@ Line 47: / Line 49: @@
 * Verify state - Use asserts to check object's state.
 * Teardown - Clean up resources.

Fukakai at 15:12, 25 September 2020

2020-09-25T15:12:43Z

← Older revision		Revision as of 17:12, 25 September 2020
Line 25:		Line 25:
	===Stubbing Variations===		===Stubbing Variations===
	* Argument Matchers		* Argument Matchers
			==Spy==
			A Spy is a Stub than is also collecting informations during the test
			** How many times this method is called ?
			** Is this method is called at least once ?
	==Mock==		==Mock==
	Fullclass with implementation, same comportement as in real code.		Fullclass with implementation, same comportement as in real code.

Fukakai at 15:10, 25 September 2020

2020-09-25T15:10:38Z

← Older revision		Revision as of 17:10, 25 September 2020
Line 12:		Line 12:
	Mocks vs Stubs = Behavioral testing vs State testing		Mocks vs Stubs = Behavioral testing vs State testing
	==Stubbing==		==Stubbing==
			Empty class, only return the expected
	* cannot be dinamically created from code		* cannot be dinamically created from code
	<source lang="Java">		<source lang="Java">
Line 25:		Line 26:
	* Argument Matchers		* Argument Matchers
	==Mock==		==Mock==
			Fullclass with implementation, same comportement as in real code.
	* Creating Objects that simulate the behavior of real objects		* Creating Objects that simulate the behavior of real objects
	* can be dynamically created from code - at runtime		* can be dynamically created from code - at runtime

Fukakai: Page créée avec « =Before & After= ===@Before @After=== The method with this annotation is executed before or after every test method ===@BeforeClass @AfterClass=== The method with this ann... »

2020-09-25T15:06:35Z

Page créée avec « =Before & After= ===@Before @After=== The method with this annotation is executed before or after every test method ===@BeforeClass @AfterClass=== The method with this ann... »

New page

=Before & After=
===@Before @After===
The method with this annotation is executed before or after every test method
===@BeforeClass @AfterClass===
The method with this annotation is executed before or after every test class

=Parametrize Test=
* On top of the test class @RunWith(Parameterized.class)
* method annotated with @Parameter is passing Arrays.asList()

=Mockito=
Mocks vs Stubs = Behavioral testing vs State testing
==Stubbing==
* cannot be dinamically created from code
<source lang="Java">
MyMockedService myMockedService = new MyMockedService();
stub(myMockedService.methodToTest("param")).return("value");
</source>
===Test lifecycle with stubs:===
* Setup - Prepare object that is being tested and its stubs collaborators.
* Exercise - Test the functionality.
* Verify state - Use asserts to check object's state.
* Teardown - Clean up resources.
===Stubbing Variations===
* Argument Matchers
==Mock==
* Creating Objects that simulate the behavior of real objects
* can be dynamically created from code - at runtime
* offer more fonctionnalities than stubbing
** How many times this method is called ?
** Is this method is called at least once ?
<source lang="Java">
MyMockedService myMockedService = mock(MyMockService.class);
when(myMockedService.methodToTest("param")).thenReturn("value");
</source>
===Test lifecycle with mocks===
* Setup data - Prepare object that is being tested.
* Setup expectations - Prepare expectations in mock that is being used by primary object.
* Exercise - Test the functionality.
* Verify expectations - Verify that correct methods has been invoked in mock.
* Verify state - Use asserts to check object's state.
* Teardown - Clean up resources.