|
- Mockito framework site
A landing page for information about Mockito framework, a mocking framework for unit tests written in Java
- Mockito (Mockito 2. 2. 7 API)
Mockito now preserves annotations on mocked methods and types as well as generic meta data Previously, a mock type did not preserve annotations on types unless they were explicitly inherited and never retained annotations on methods As a consequence, the following conditions now hold true: @MyAnnotation class Foo { List<String> bar() { } }
- InjectMocks (Mockito 2. 2. 7 API)
Mockito will try to inject mocks only either by constructor injection, setter injection, or property injection in order and as described below If any of the following strategy fail, then Mockito won't report failure; i e you will have to provide dependencies yourself
- ArgumentMatchers (Mockito 2. 2. 7 API)
With Java 8 this method will be removed in Mockito 3 0 This method is only used for generic friendliness to avoid casting, this is not anymore needed in Java 8
- ArgumentCaptor (Mockito 2. 2. 7 API)
Mockito verifies argument values in natural java style: by using an equals () method This is also the recommended way of matching arguments because it makes tests clean simple
- MockitoAnnotations (Mockito 2. 2. 7 API)
Initializes objects annotated with Mockito annotations for given testClass: @ Mock, @ Spy, @ Captor, @ InjectMocks See examples in javadoc for MockitoAnnotations class
- Spy (Mockito 2. 2. 7 API)
Mockito doesn't mock final methods so the bottom line is: when you spy on real objects + you try to stub a final method = trouble Also you won't be able to verify those method as well
- BDDMockito (Mockito 2. 2. 7 API)
public class BDDMockito extends Mockito Behavior Driven Development style of writing tests uses given when then comments as fundamental parts of your test methods This is exactly how we write our tests and we warmly encourage you to do so! Start learning about BDD here: http: en wikipedia org wiki Behavior_Driven_Development
|
|
|