Best Mockito code snippet using org.mockitousage.spies.SpyingOnRealObjectsTest.shouldVerify
Source: SpyingOnRealObjectsTest.java
...20public class SpyingOnRealObjectsTest extends TestBase {21 List<String> list = new LinkedList<String>();22 List<String> spy = Mockito.spy(list);23 @Test24 public void shouldVerify() {25 spy.add("one");26 spy.add("two");27 Assert.assertEquals("one", spy.get(0));28 Assert.assertEquals("two", spy.get(1));29 Mockito.verify(spy).add("one");30 Mockito.verify(spy).add("two");31 }32 @SuppressWarnings({ "CheckReturnValue", "MockitoUsage" })33 @Test34 public void shouldBeAbleToMockObjectBecauseWhyNot() {35 Mockito.spy(new Object());36 }37 @Test38 public void shouldStub() {39 spy.add("one");40 Mockito.when(spy.get(0)).thenReturn("1").thenReturn("1 again");41 Assert.assertEquals("1", spy.get(0));42 Assert.assertEquals("1 again", spy.get(0));43 Assert.assertEquals("one", spy.iterator().next());44 Assert.assertEquals(1, spy.size());45 }46 @Test47 public void shouldAllowOverridingStubs() {48 Mockito.when(spy.contains(ArgumentMatchers.anyObject())).thenReturn(true);49 Mockito.when(spy.contains("foo")).thenReturn(false);50 Assert.assertTrue(spy.contains("bar"));51 Assert.assertFalse(spy.contains("foo"));52 }53 @Test54 public void shouldStubVoid() {55 Mockito.doNothing().doThrow(new RuntimeException()).when(spy).clear();56 spy.add("one");57 spy.clear();58 try {59 spy.clear();60 Assert.fail();61 } catch (RuntimeException e) {62 }63 Assert.assertEquals(1, spy.size());64 }65 @Test66 public void shouldStubWithDoReturnAndVerify() {67 Mockito.doReturn("foo").doReturn("bar").when(spy).get(0);68 Assert.assertEquals("foo", spy.get(0));69 Assert.assertEquals("bar", spy.get(0));70 Mockito.verify(spy, Mockito.times(2)).get(0);71 Mockito.verifyNoMoreInteractions(spy);72 }73 @Test74 public void shouldVerifyInOrder() {75 spy.add("one");76 spy.add("two");77 InOrder inOrder = Mockito.inOrder(spy);78 inOrder.verify(spy).add("one");79 inOrder.verify(spy).add("two");80 Mockito.verifyNoMoreInteractions(spy);81 }82 @Test83 public void shouldVerifyInOrderAndFail() {84 spy.add("one");85 spy.add("two");86 InOrder inOrder = Mockito.inOrder(spy);87 inOrder.verify(spy).add("two");88 try {89 inOrder.verify(spy).add("one");90 Assert.fail();91 } catch (VerificationInOrderFailure f) {92 }93 }94 @Test95 public void shouldVerifyNumberOfTimes() {96 spy.add("one");97 spy.add("one");98 Mockito.verify(spy, Mockito.times(2)).add("one");99 Mockito.verifyNoMoreInteractions(spy);100 }101 @Test102 public void shouldVerifyNumberOfTimesAndFail() {103 spy.add("one");104 spy.add("one");105 try {106 Mockito.verify(spy, Mockito.times(3)).add("one");107 Assert.fail();108 } catch (TooLittleActualInvocations e) {109 }110 }111 @Test112 public void shouldVerifyNoMoreInteractionsAndFail() {113 spy.add("one");114 spy.add("two");115 Mockito.verify(spy).add("one");116 try {117 Mockito.verifyNoMoreInteractions(spy);118 Assert.fail();119 } catch (NoInteractionsWanted e) {120 }121 }122 @Test123 public void shouldToString() {124 spy.add("foo");125 Assert.assertEquals("[foo]", spy.toString());126 }...
Multiple RunWith Statements in jUnit
mockito anyList of a given size
when I run mockito test occurs WrongTypeOfReturnValue Exception
Mockito - separately verifying multiple invocations on the same method
@InjectMocks, the constructor or the initialization block threw an exception
Final method mocking
Android instrumentation tests with Mockito
PowerMock + Mockito VS Mockito alone
Mockito - Wanted but not invoked: Actually, there were zero interactions with this mock
Mock a constructor with parameter
You cannot do this because according to spec you cannot put the same annotation twice on the same annotated element.
So, what is the solution? The solution is to put only one @RunWith()
with runner you cannot stand without and replace other one with something else. In your case I guess you will remove MockitoJUnitRunner
and do programatically what it does.
In fact the only thing it does it runs:
MockitoAnnotations.initMocks(test);
in the beginning of test case. So, the simplest solution is to put this code into setUp()
method:
@Before
public void setUp() {
MockitoAnnotations.initMocks(this);
}
I am not sure, but probably you should avoid multiple call of this method using flag:
private boolean mockInitialized = false;
@Before
public void setUp() {
if (!mockInitialized) {
MockitoAnnotations.initMocks(this);
mockInitialized = true;
}
}
However better, reusable solution may be implemented with JUnt's rules.
public class MockitoRule extends TestWatcher {
private boolean mockInitialized = false;
@Override
protected void starting(Description d) {
if (!mockInitialized) {
MockitoAnnotations.initMocks(this);
mockInitialized = true;
}
}
}
Now just add the following line to your test class:
@Rule public MockitoRule mockitoRule = MockitoJUnit.rule();
and you can run this test case with any runner you want.
Check out the latest blogs from LambdaTest on this topic:
“Test frequently and early.” If you’ve been following my testing agenda, you’re probably sick of hearing me repeat that. However, it is making sense that if your tests detect an issue soon after it occurs, it will be easier to resolve. This is one of the guiding concepts that makes continuous integration such an effective method. I’ve encountered several teams who have a lot of automated tests but don’t use them as part of a continuous integration approach. There are frequently various reasons why the team believes these tests cannot be used with continuous integration. Perhaps the tests take too long to run, or they are not dependable enough to provide correct results on their own, necessitating human interpretation.
Hey everyone! We hope you had a great Hacktober. At LambdaTest, we thrive to bring you the best with each update. Our engineering and tech teams work at lightning speed to deliver you a seamless testing experience.
Hey LambdaTesters! We’ve got something special for you this week. ????
JUnit is one of the most popular unit testing frameworks in the Java ecosystem. The JUnit 5 version (also known as Jupiter) contains many exciting innovations, including support for new features in Java 8 and above. However, many developers still prefer to use the JUnit 4 framework since certain features like parallel execution with JUnit 5 are still in the experimental phase.
Learn to execute automation testing from scratch with LambdaTest Learning Hub. Right from setting up the prerequisites to run your first automation test, to following best practices and diving deeper into advanced test scenarios. LambdaTest Learning Hubs compile a list of step-by-step guides to help you be proficient with different test automation frameworks i.e. Selenium, Cypress, TestNG etc.
You could also refer to video tutorials over LambdaTest YouTube channel to get step by step demonstration from industry experts.
Get 100 minutes of automation test minutes FREE!!