-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RestResponse.assertBody behavior is broken #177
Comments
@paulodamaso/z this project will fix the problem faster if you donate a few dollars to it; just click here and pay via Stripe, it's very fast, convenient and appreciated; thanks a lot! |
@yegor256 @paulodamaso after some investigation (for yegor256/takes#800), I think the problem is not with Take those four examples (using takes). Expected empty body: it fails, because the body, according to
The same with
Now expecting a body, it's even worse, the returned body is:
But if you use
I have also tested the same test with rest-assured instead of jcabi-http, and it passes without any problem. |
@yegor256 ping |
@yegor256 What do you think about it? If this ticket is valid please put it on scope, we have a ticket on takes that depends on it. |
@paulodamaso done |
Job #177 is now in scope, role is |
Bug was reported, see §29: +15 point(s) just awarded to @paulodamaso/z |
@yegor256 assign to me |
RestResponse.assertBody
behavior is broken: it is checking all the Response string when it should only check the body part of string.This makes impossible for testing when we got an empty message body from server, because
assertBody
considers header section too when asserting if message body has some content.Please refer to
FtRemotesTest
on https://github.com;yegor256/takes to see how this method is misbehaving.The text was updated successfully, but these errors were encountered: