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
does not record the request body or params e.g. when using .formParams().
I tried setting a custom RestReportingHelper that adds .withParameters() to the rest query, but there was no change in the generated report.
My dependencies are:
serenity-jbehave:1.4.6
serenity-core: 2.2.1
serenity-rest-assured:2.2.1
serenity-junit: 2.2.1
Upgrading the dependencies to 2.2.4 did not fix the issue
The text was updated successfully, but these errors were encountered:
SengCheong
changed the title
SerenityRest not reporting Request Body in HTML Report
SerenityRest not reporting Request Params in HTML Report
May 9, 2020
Sorry Wakaleo, I have been busy and I did not had the time into looking for a possible solution. From my understanding, it seems that the problem might also extend all the way into the way the HTML report is generated, especially regarding the HTMLAcceptanceTestReporter.java class
I do not have the time currently to investigate how the HTMLAcceptanceTestReporter works at the moment, so I highly suggest you tag this issue as a bug currently. I will see if i am avaliable to propose a PR
Hi,
I am unable to view the request body when issuing a rest-assured request with SerenityRest.
This is in contrast to the screenshot present in this tutorial book:
https://serenity-bdd.github.io/theserenitybook/0.1.0/serenity-rest.html
I performed an initial analysis, and discovered that:
serenity-core/serenity-rest-assured/src/main/java/net/serenitybdd/rest/utils/RestReportingHelper.java
Lines 44 to 62 in fcbcb27
does not record the request body or params e.g. when using .formParams().
I tried setting a custom RestReportingHelper that adds .withParameters() to the rest query, but there was no change in the generated report.
My dependencies are:
Upgrading the dependencies to 2.2.4 did not fix the issue
The text was updated successfully, but these errors were encountered: