Java 模拟方法实现Junit mockito
我正在尝试测试以下类:Java 模拟方法实现Junit mockito,java,junit,mocking,mockito,Java,Junit,Mocking,Mockito,我正在尝试测试以下类: public class PreprocessorServiceImpl implements PreprocessorService { private static final Logger LOG = LoggerFactory.getLogger( PreprocessorServiceImpl.class ); private FileServiceProvider fileServiceProvider; private PreProcessorApiS
public class PreprocessorServiceImpl implements PreprocessorService
{
private static final Logger LOG = LoggerFactory.getLogger( PreprocessorServiceImpl.class );
private FileServiceProvider fileServiceProvider;
private PreProcessorApiService preprocessorApiService;
private ScanProcessingHelper scanProcessingHelper;
private DocumentProcessingService docProcessingService;
private CacheTimeOutHandler cacheTimeHandler;
private DocumentEventLogger docEventLogger;
private ScanProcessingService scanProcessingService;
private EventLogger eventLogger;
private ScanTrackLogger scanTrackLogger;
//Getters and setters.
@Override
public void processDocument( KafkaDocumentMetaData kafkaDocumentMeta )
{
APIKeyConfigurationVO apiConfigurationsVo = kafkaDocumentMeta.getCustomerConfiguration();
DocumentRequest documentRequest = kafkaDocumentMeta.getDocumentRequest();
LOG.info( "Started preprocessing for documentId: {}", documentRequest.getDocumentId() );
PreprocessorApiResponse apiResponse;
try {
byte[] documentInBytes = getDocumentFileInBytes( documentRequest, apiConfigurationsVo ); //Download from cloud
docEventLogger.logDocIdEvent( documentRequest.getDocumentId(), EventEnum.FILE_DOWNLOADED );
apiResponse = preprocessorApiService.preProcess(
documentRequest.getDocumentRequestAdditionalInfo().getPreProcessingModelUrl(), documentInBytes,
documentRequest.getDocumentId() );
documentRequest.setPreprocessorApiResponse( apiResponse );
} catch ( Exception e ) {
//If download / ML api failed unexpectedly, then mark it for failure
handleFailure( documentRequest, apiConfigurationsVo, e );
return;
}
//code to process further in case of success
}
private void handleFailure( DocumentRequest documentRequest, APIKeyConfigurationVO apiConfigurationsVo, Throwable thr )
{
LOG.error( "Exception occured while processing document. marking it as failed.", thr );
docProcessingService.persistAndModify( documentRequest, DocumentStatus.FAILED, cacheTimeHandler.getDocumentTimeOut() );//to redis
docProcessingService.publishDocumentReqMeta( documentRequest, apiConfigurationsVo );//to result analyzer
docEventLogger.logDocIdFailureEvent( documentRequest.getDocumentId(), thr );
}
}
在docProcessingService.persistAndModify()中有一个更新对象状态的方法
documentRequest.setStatus(documentStatus.getStatus())代码>
详情如下:
public void persistAndModify( DocumentRequest documentRequest, DocumentStatus documentStatus, int timeToLive )
{
LOG.debug( "Persisting document request with document id {} and status {}", documentRequest.getDocumentId(),
documentRequest.getStatus() );
documentRequest.setStatus( documentStatus.getStatus() );
persistResponse( documentRequest.getDocumentId(), documentRequest, timeToLive );
LOG.info( "Updated document request and status to: {} for documentId: {}", documentRequest.getStatus(),
documentRequest.getDocumentId() );
}
我不想执行完整的方法。但只需将documentRequest
的状态设置为documentStatus
。这是否可以使用junit mockito实现
我尝试使用doAnswer
,但它抛出了NPE。下面是我的代码
Mockito.doAnswer( invocation -> {
Object[] args = invocation.getArguments();
DocumentRequest modified = ( (DocumentRequest) args[0] );
modified.setStatus( DocumentStatus.FAILED.getStatus() );
return null;
} ).when( docProcessingService ).persistAndModify( any(), any(), any() );
//.
//.data population code
//.
assertEquals( docRequest.getStatus(), DocumentStatus.INITIATED.getStatus() );
preprocessorService.processDocument( kafkaMessage );
assertEquals( docRequest.getStatus(), DocumentStatus.FAILED.getStatus() );
它将NPE抛向
}).when(docProcessingService).persistAndModify(any(),any(),any())代码>
我已经补充了-
@RunWith(MockitoJUnitRunner.class)
和
MockitoAnnotations.initMocks(preprocessorservicests.class)代码>
并使用@Mock进行模拟
@Mock
private DocumentProcessingService docProcessingService;
doAnswer
是否适合我的用例,或者是否还有其他内容?如何在模拟的同时给出方法实现
如果这是一个愚蠢的问题,请原谅。我不熟悉使用mockito
编辑:添加堆栈跟踪
java.lang.NullPointerException
at my.package.service.PreprocessorServiceTests.testDocumentDownloadFailure(PreprocessorServiceTests.java:114)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.mockito.internal.runners.DefaultInternalRunner$1$1.evaluate(DefaultInternalRunner.java:44)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.mockito.internal.runners.DefaultInternalRunner$1.run(DefaultInternalRunner.java:74)
at org.mockito.internal.runners.DefaultInternalRunner.run(DefaultInternalRunner.java:80)
at org.mockito.internal.runners.StrictRunner.run(StrictRunner.java:39)
at org.mockito.junit.MockitoJUnitRunner.run(MockitoJUnitRunner.java:163)
at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
at org.junit.vintage.engine.execution.RunnerExecutor.execute(RunnerExecutor.java:40)
at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
at java.util.Iterator.forEachRemaining(Iterator.java:116)
at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
at org.junit.vintage.engine.VintageTestEngine.executeAllChildren(VintageTestEngine.java:80)
at org.junit.vintage.engine.VintageTestEngine.execute(VintageTestEngine.java:71)
at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:220)
at org.junit.platform.launcher.core.DefaultLauncher.lambda$execute$6(DefaultLauncher.java:188)
at org.junit.platform.launcher.core.DefaultLauncher.withInterceptedStreams(DefaultLauncher.java:202)
at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:181)
at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:128)
at org.eclipse.jdt.internal.junit5.runner.JUnit5TestReference.run(JUnit5TestReference.java:89)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)
编辑2:
我删除了doAnswer,发现下面两个语句也抛出了NPE
Mockito.doNothing().when( docProcessingService ).persistAndModify( any(), any(), any() );
verify( docProcessingService, times( 1 ) ).persistAndModify( any(), DocumentStatus.FAILED, any() );
因此,我认为这与void返回类型有关,而不是doAnswer()
来自同一依赖项的以下语句工作正常,没有任何问题
when( docProcessingService.publishDocumentReqMeta( any(), any() ) ).thenReturn( true );
以下是相同的方法签名
public boolean publishDocumentReqMeta( DocumentRequest docRequest, APIKeyConfigurationVO apiKeyConfiguration )
我不想执行完整的方法。但只需将documentRequest的状态设置为documentStatus。这是否可以使用junit mockito实现
不,不是,因为这不是你想做的。您希望测试该方法是否执行了它应该执行的所有操作,即更新请求状态和persistResponse
如果要单独测试它们,请创建单独的方法。您还可以考虑将持久化部分分割成一个完全分离的类,例如
class DocumentProcessingService {
private Persistor persistor;
public void persistAndModify( DocumentRequest documentRequest, DocumentStatus documentStatus, int timeToLive ) {
documentRequest.getStatus() );
documentRequest.setStatus( documentStatus.getStatus() );
persistor.persistResponse( documentRequest.getDocumentId(), documentRequest, timeToLive );
documentRequest.getDocumentId() );
}
}
然后,您可以通过
@RunWith(MockitoJUnitRunner.class)
class ProcessingServiceTest {
@InjectMocks private DocumentProcessingService sut;
@Mock private Persistor persistor;
@Test
public void testPersistAndModify() {
DocumentRequest request = mock(DocumentRequest.class);
when(request.getDocumentId()).thenReturn(id);
DocumentStatus status = mock(DocumentStatus.class);
when(status.getStatus).thenReturn(someStatus);
sut.persistAndModify(request, status, x);
// check status was updated
verify(documentRequest).setStatus(someStatus);
// check document was persisted
verify(persistor).persistResponse(id, request, x);
}
}
您实际的persistResponse
代码很可能就是这样做的,因此您可以在不重构的情况下验证这一点
编辑:
在您编辑之后,我不会更新上述代码,您必须自己替换相应的代码段。简而言之,您必须模拟docEventLogger.logDocIdEvent
和预处理服务.preProcess
调用
最大的问题是“从云下载”部分,您可能还想将该代码移动到外部类中,以便您也可以模拟该下载部分。@second添加了stacktrace。传递此
没有帮助。我想确认一下,这就是我们应该如何使用doAnswer()
?您要测试的类是什么?你能发布它的最小代码(即,测试中的方法)吗?“在你的测试中,你到底把它叫做什么?”达尼奥更新了帖子。我已经添加了我正在测试的类preprocesserviceimpl
尝试使用anyInt
作为最后一个参数。非常感谢@second。将any()
更改为anyInt()
是一个技巧。而参数匹配器的无效使用3名游行者预计,2名记录的
发生,因为我使用的是DocumentStatus。失败
而不是any()
。在我看来,他不想测试持久化和修改
方法本身。这似乎是一个依赖项的方法(有一些副作用)。@second这就是为什么您只需验证该方法是否被调用(verify(dependency)。persist()
正是这样做的)。没错@second。下载失败时,Im正在测试预处理器ServiceImpl.processDocument()
。发生这种情况时,我希望确保文档状态更新为“失败”。基本上确保调用了handleFailure()
。但这是一个私人问题method@daniu:verify
如果副作用是相关的(为了进一步的测试执行),那么可能还不够。对于正确的实现,您通常希望避免此类事情。返回更新的实体可能是一个选项。集成测试可能更适合这种情况。