不例外的Gavel/Dredd测试失败

Question

有人能帮我找出这个Dredd测试失败的原因吗？在我看来很好：

fail: GET /device/2/battery duration: 260ms
fail: body: Real and expected data does not match.

request: 
body: 

headers: 
    User-Agent: Dredd/0.6.0 (Darwin 14.3.0; x64)

uri: /device/2/battery
method: GET


expected: 
headers: 
    connection: Keep-Alive
    content-length: 18
    content-type: text/plain

body: 
BATTERY REQ QUEUED

statusCode: 200


actual: 
statusCode: 200
headers: 
    connection: Keep-Alive
    content-length: 18
    content-type: text/plain
    date: Tue, 09 Jun 2015 19:01:59 GMT

body: 
BATTERY REQ QUEUED

Answer 1

这些可疑的错误通常是由预期的或真实的身体中的尾换行符引起的。试着用CLI蓝图解析器解析您的蓝图，看看Dredd到底期望什么。

有这在文档中给出了一个解决办法的提示。。