You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to request the option to automatically include the response body in the exception message when a request validation fails.
Before you ask, we are already using the config that logs requests when validation fails. This works, but takes extra manual effort to find the response in our logs. We are running our RestAssured tests using Jenkins, which analyzes the TestNG result and shows the name of each failed test, and links to the exception message and stack trace. However, the exception is not linked to the console log! We have to go into the console log (which is several megabytes, because our test suite is huge and has a lot of noise) to manually search for it.
It would be really nice if the response body was included in that exception message, so we don't have to go searching for it. A lot of times, assertion errors look the same ("Expected status code 200 but was 422"), but the body clarifies the error (e.g. "The job is already running").
I looked into the code and suspect something could be added to this line of validate(Response) method, but I am not a Groovy developer....
The text was updated successfully, but these errors were encountered:
I would like to request the option to automatically include the response body in the exception message when a request validation fails.
Before you ask, we are already using the config that logs requests when validation fails. This works, but takes extra manual effort to find the response in our logs. We are running our RestAssured tests using Jenkins, which analyzes the TestNG result and shows the name of each failed test, and links to the exception message and stack trace. However, the exception is not linked to the console log! We have to go into the console log (which is several megabytes, because our test suite is huge and has a lot of noise) to manually search for it.
It would be really nice if the response body was included in that exception message, so we don't have to go searching for it. A lot of times, assertion errors look the same ("Expected status code 200 but was 422"), but the body clarifies the error (e.g. "The job is already running").
I looked into the code and suspect something could be added to this line of
validate(Response)
method, but I am not a Groovy developer....The text was updated successfully, but these errors were encountered: