在Spring Rest Docs中记录byte []响应

Question

我正在使用Spring Rest Docs（1.1.1.RELEASE）构建一个API并记录它，并且有一个将图像作为字节数组返回的api。

我需要描述REST文档中的响应类型。我不知道这是如何使用FieldDescriptor

做当我尝试：

//get mock byte array 
byte[] attachment = "Hello".getBytes(); 

FieldDescriptor[] contentFields = new FieldDescriptor[] { 
      fieldWithPath("").type(byte[].class) 
        .description("bytes of the attachment ")}; 

    when(serviceMock.getImage("fe329638007b4ea3b2a5")).thenReturn(attachment); 

    this.mockMvc 
      .perform(RestDocumentationRequestBuilders.get("/api/v1/contents/{contentId}/images", "fe329638007b4ea3b2a5")) 
      .andExpect(status().isOk()).andDo(document("{method-name}", 
        pathParameters(parameterWithName("contentId").description("The id of the Content")), 
        responseFields(contentFields))); 

    verify(serviceMock, times(1)).getImage("fe329638007b4ea3b2a5"); 
    verifyNoMoreInteractions(serviceMock); 

我得到下面的错误

org.springframework.restdocs.payload.PayloadHandlingException: com.fasterxml.jackson.core.JsonParseException: Unrecognized token 'Hello': was expecting ('true', 'false' or 'null') 
at [Source: [B@13866865; line: 1, column: 11] 
at org.springframework.restdocs.payload.JsonContentHandler.readContent(JsonContentHandler.java:86) 
at org.springframework.restdocs.payload.JsonContentHandler.findMissingFields(JsonContentHandler.java:52) 
at org.springframework.restdocs.payload.AbstractFieldsSnippet.validateFieldDocumentation(AbstractFieldsSnippet.java:152) 
at org.springframework.restdocs.payload.AbstractFieldsSnippet.createModel(AbstractFieldsSnippet.java:100) 
at org.springframework.restdocs.snippet.TemplatedSnippet.document(TemplatedSnippet.java:64) 
at org.springframework.restdocs.generate.RestDocumentationGenerator.handle(RestDocumentationGenerator.java:196) 
at org.springframework.restdocs.mockmvc.RestDocumentationResultHandler.handle(RestDocumentationResultHandler.java:55) 
at org.springframework.test.web.servlet.MockMvc$1.andDo(MockMvc.java:177) 
at com.davita.comms.controller.CommsControllerTest.getThumbnailByContentId(CommsControllerTest.java:205) 
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:497) 
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.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:75) 
at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:86) 
at org.springframework.restdocs.JUnitRestDocumentation$1.evaluate(JUnitRestDocumentation.java:55) 
at org.junit.rules.RunRules.evaluate(RunRules.java:20) 
at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:84) 
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) 
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:252) 
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:94) 
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.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61) 
at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:70) 
at org.junit.runners.ParentRunner.run(ParentRunner.java:363) 
at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:191) 
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) 
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) 
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) 
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:670) 
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) 
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) 

有没有办法在FieldDescriptor提及的是，返回的数据不是json，所以没有道理。

是否有任何其他方式可以在没有FieldDescriptors的情况下对其进行记录？

Answer 1

REST Docs不支持记录二进制有效内容的内容。请求和响应字段片段用于记录JSON或XML有效负载的结构。

我不认为使用REST Docs生成表来描述二进制响应的好处并不多，因为没有太多可以断言的东西。任何响应都可以视为一个字节[]，因为这是最原始形式的响应。例如，JSON和XML一样是一个byte []。它们只是对其内容有特别限制的字节数组。

与其试图使用REST文档生成表来描述二进制响应，我只是将其硬编码到您的.adoc文件中。如果你想在你的测试中包含一些关于响应内容的断言，那么我会使用一些MockMvc的匹配器。例如，您可以断言响应正文与您配置模拟服务返回的字节匹配。