TestNG Mockito，如何测试抛出的异常和对mock的调用

Question

在我的TestNG单元测试中，我有一个场景，我想测试，抛出了一个异常，但我也想测试一些方法没有在模拟子组件上调用。我想出了这个，但这个很难看，很长，可读性不好：

@Test
public void testExceptionAndNoInteractionWithMethod() throws Exception {

    when(subComponentMock.failingMethod()).thenThrow(RuntimeException.class);

    try {
        tested.someMethod(); //may call subComponentMock.methodThatShouldNotBeCalledWhenExceptionOccurs
    } catch (RuntimeException e) {
        verify(subComponentMock, never()).methodThatShouldNotBeCalledWhenExceptionOccurs(any());
        return;
    }

    fail("Expected exception was not thrown");
}

有没有更好的解决方案来测试异常和verify（）方法？

Answer 1

我将通过创建两个测试并使用注释属性expectedExceptions和dependsOnMethods来分离这两个问题。

@Test(expectedExceptions = { RuntimeExpcetion.class } )
public void testException() {
    when(subComponentMock.failingMethod()).thenThrow(RuntimeException.class);
    tested.someMethod(); //may call subComponentMock.methodThatShouldNotBeCalledWhenExceptionOccurs
}

@Test(dependsOnMethods = { "testException" } )
public void testNoInteractionWithMethod() {
    verify(subComponentMock, never()).methodThatShouldNotBeCalledWhenExceptionOccurs(any());
}

对我来说，它看起来更整洁。您摆脱了try cat块和不必要的失败方法调用。

Answer 2

我们决定使用断言框架。

when(subComponentMock.failingMethod()).thenThrow(RuntimeException.class);

Assertions.assertThatThrownBy(() -> tested.someMethod()).isOfAnyClassIn(RuntimeException.class);

verify(subComponentMock, never()).methodThatShouldNotBeCalledWhenExceptionOccurs(any());