Mockito Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
=Overview= | =Overview= | ||
Mockito works by dynamically creating proxies that intercept invocation into the [[Mockito_Concepts#Managed_Test_Double|managed test double]] objects and reacting the way they were programmed - return pre-defined answers, throw exceptions, etc. when the invocations are sent into the managed test doubles. | |||
=MockitoJUnitRunner= | =MockitoJUnitRunner= | ||
=<tt>Mockito.mock()</tt>= | =<tt>Mockito.mock()</tt>= | ||
Revision as of 04:29, 16 July 2021
Internal
Overview
Mockito works by dynamically creating proxies that intercept invocation into the managed test double objects and reacting the way they were programmed - return pre-defined answers, throw exceptions, etc. when the invocations are sent into the managed test doubles.
MockitoJUnitRunner
Mockito.mock()
@Mock
Can't Mock
- Final classes
- Final methods
- Enums
- Static methods
- Private methods
hashCode()andequals()methods- Anonymous classes
- Primitive types
PowerMock can mock these constructs.
Managed Test Double
A test double managed by Mockito. It can be created either via the API with Mockito.mock(<object>) or by annotating the field referencing the object in question with @Mock.