-
Deprecated Interfaces
-
Deprecated ClassesClassDescriptionnot part of the public API, use
BDDMockito.BDDMyOngoingStubbing
instead.not part of the public API, useBDDMockito.BDDStubber
instead.
-
Deprecated EnumsEnumDescription
-
Deprecated Annotation Types
-
Deprecated MethodsMethodDescriptionPlease use
AnnotationEngine.process(Class, Object)
method instead that is more robustCreates mock, ArgumentCaptor or wraps field instance in spy object. Only if of correct annotation type.
Please useIMockitoConfiguration.getDefaultAnswer()
Steps:
1. Leave the implementation of getReturnValues() method empty - it's not going to be used anyway.
2. Implement getDefaultAnswer() instead.
In rare cases your code might not compile with recent deprecation & changes. Very sorry for inconvenience but it had to be done in order to keep framework consistent.
See javadoc
ReturnValues
for info why this method was deprecatedAllows configuring the default return values of unstubbed invocations
See javadoc for
IMockitoConfiguration
Please use mock(Foo.class, defaultAnswer);UseMockito.doThrow(Throwable)
method for stubbing voidsDeprecated Validation with timeout combined with never simply does not make sense, as atMost() will typically immediately pass, and therefore not wait the timeout. The behaviour you may be looking for is actually provided by after().atMost().To avoid compilation errors upon upgrade the method is deprecated and it throws a "friendly reminder" exception.
In a future release we will remove timeout(x).atMost(y) and timeout(x).never() from the API.
Do you want to find out more? See issue 235
Validation with timeout combined with never simply does not make sense, as never() will typically immediately pass, and therefore not wait the timeout. The behaviour you may be looking for is actually provided by after().never().To avoid compilation errors upon upgrade the method is deprecated and it throws a "friendly reminder" exception.
In a future release we will remove timeout(x).atMost(y) and timeout(x).never() from the API.
Do you want to find out more? See issue 235
-
Deprecated ConstructorsConstructorDescriptionPlease use factory method
ArgumentCaptor.forClass(Class)
to create captorsThis is required to avoid NullPointerExceptions when autoUnboxing primitive types. See issue 99.
Example:
ArgumentCaptor<Person> argument = ArgumentCaptor.forClass(Person.class); verify(mock).doSomething(argument.capture()); assertEquals("John", argument.getValue().getName());
Answer
interfaceIn rare cases your code might not compile with recent deprecation & changes. Very sorry for inconvenience but it had to be done in order to keep framework consistent.
Why it is deprecated? ReturnValues is being replaced by Answer for better consistency & interoperability of the framework. Answer interface has been in Mockito for a while and it has the same responsibility as ReturnValues. There's no point in mainting exactly the same interfaces.
Configures return values for an unstubbed invocation
Can be used in
Mockito.mock(Class, ReturnValues)