[英]PowerMock with EasyMock, expectation returns null instead of a mock
寻找有关为何期望返回null而不是请求的模拟的指导。 有问题的模拟是“未来”,并且遵循与正确返回的其他模拟相同的模式。
为了向具有powermock和easymock经验的人提供所有信息,我提供了所有代码,包括受测代码和设置模拟和行为的测试代码。 有问题的期望是
EasyMock.expect( mockAsyncClient.execute( EasyMock.isA( HttpGet.class ),
EasyMOck.isA( HttpClientContext.class ), isNull() ).andReturn( mockFuture )
它产生一个null而不是返回一个模拟的Future。
任何想法,将不胜感激。
ps有很多模拟安装程序需要测试此功能,我希望这不会妨碍评估问题。 任何删除不必要的模拟基础设施的建议将不胜感激。
这是测试中的代码
public <T> T getResponse( ResponseHandler<T> responseHandler )
throws IOException, InterruptedException, ExecutionException
{
String connectTo = buildUri();
try( CloseableHttpAsyncClient httpClient =
HttpAsyncClients.custom()
.setConnectionManager( connManager )
.build() ) {
HttpGet request = new HttpGet( connectTo );
HttpClientContext ctx = HttpClientContext.create();
addHeaders( request );
httpClient.start();
Future<HttpResponse> futureResponse = httpClient.execute( request, ctx, null ); //<-- this line executes using a verified HttpClient mock but returns null
HttpResponse response = futureResponse.get();
return responseHandler.handleResponse( response );
}
}
测试代码:
@Test
@PrepareOnlyThisForTest( { HttpAsyncClients.class, HttpAsyncClientBuilder.class } )
public void testGetResponseCallsResponseHandler()
throws IOException, InterruptedException, ExecutionException
{
// create mocks to be used when exercising the code under test
CloseableHttpAsyncClient mockAsyncClient =
EasyMock.createMock( CloseableHttpAsyncClient.class );
PowerMock.mockStatic( HttpAsyncClients.class );
HttpAsyncClientBuilder mockClientBuilder =
PowerMock.createMock( HttpAsyncClientBuilder.class );
HttpAsyncClientBuilder mockClientBuilder2 =
PowerMock.createMock( HttpAsyncClientBuilder.class );
HttpResponse mockResponse = PowerMock.createMock( HttpResponse.class );
StatusLine mockStatusLine = PowerMock.createMock( StatusLine.class );
@SuppressWarnings( "unchecked" )
Future<HttpResponse> mockFuture = PowerMock.createMock( Future.class );
// set up expectations that use the mocks
EasyMock.expect( HttpAsyncClients.custom() ).andReturn( mockClientBuilder );
EasyMock.expect( mockClientBuilder.setConnectionManager( EasyMock.isA( NHttpClientConnectionManager.class ) ) )
.andReturn( mockClientBuilder2 );
EasyMock.expect( mockClientBuilder2.build() ).andReturn( mockAsyncClient );
mockAsyncClient.start();
EasyMock.expectLastCall().once();
EasyMock.expect( mockAsyncClient.execute( EasyMock.isA( HttpGet.class ),
EasyMock.isA( HttpClientContext.class ),
EasyMock.isNull() ) )
.andReturn( mockFuture );
EasyMock.expect( mockFuture.get() ).andReturn( mockResponse );
EasyMock.expect( mockResponse.getStatusLine() ).andReturn( mockStatusLine );
EasyMock.expect( mockStatusLine.getStatusCode() ).andReturn( 200 );
mockAsyncClient.close();
EasyMock.expectLastCall().once();
PowerMock.replayAll();
ClientConfig cfg = new ClientConfigBuilder().build();
RestClient client = new RestClient( cfg );
int statusCode = client.getResponse( new ResponseHandler<Integer>() {
@Override
public Integer handleResponse( HttpResponse response )
throws ClientProtocolException, IOException
{
StatusLine statusLine = response.getStatusLine();
return statusLine.getStatusCode();
}
} );
PowerMock.verifyAll();
assertEquals( "status code incorrect", 200, statusCode );
}
我发现了问题,并且这是我确定已经遇到许多其他问题的问题之一...
我错误地使用EasyMock而不是PowerMock创建模拟的事实可以解释返回空值的模拟:
CloseableHttpAsyncClient mockAsyncClient =
EasyMock.createMock( CloseableHttpAsyncClient.class );
通过将该行更改为
CloseableHttpAsyncClient mockAsyncClient =
PowerMock.createMock( CloseableHttpAsyncClient.class );
测试通过了。
原因是PowerMock拥有用于创建的模拟,并且只能验证这些模拟的行为。 PowerMock包装了EasyMock,因此需要对受控对象进行可视化。
对于受此问题影响的人,请对问题进行投票。 不知道为什么我不赞成投票,但请使这个答案更容易发现。
谢谢,罗宾。
我在这里总结,因为我试图在类似这样的类上使用whenNew(SomeClass.class).withAnyArguments()
:
class SomeClass {
public SomeClass(String... args) { }
}
原来withAnyArguments()
与varargs不匹配。 就我而言,解决方法是:
whenNew(SomeClass.class).withArguments(Matchers.<String>anyVararg()).thenReturn(myMock);
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.