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
If we have a very long continuous string of characters in the report, like a request url that failed, it will spill out of the visible frame.
Depending on the length, the person analyzing the report will have to scroll horizontally to scan the entire string but will never have access to the whole/overview in the serenity report. As an example think of the following type of error message:
"1) Request with bad responses were found on page: Page One
Bad request:
NetworkEvent:
Request: http://site.under.test:xxxx/query?param1=1324654983655¶m2=sql%2Fexample%2Fone¶m3=value4¶m4=value4¶m5=value5¶m6=value%2F0%2F6&.....¶mN=valueN
Response: 500 Server Error"
in which the request is displayed on a single line, even if it doesn't fit in the visible frame of the report
The text was updated successfully, but these errors were encountered:
If we have a very long continuous string of characters in the report, like a request url that failed, it will spill out of the visible frame.
Depending on the length, the person analyzing the report will have to scroll horizontally to scan the entire string but will never have access to the whole/overview in the serenity report.
As an example think of the following type of error message:
"1) Request with bad responses were found on page: Page One
Bad request:
NetworkEvent:
Request: http://site.under.test:xxxx/query?param1=1324654983655¶m2=sql%2Fexample%2Fone¶m3=value4¶m4=value4¶m5=value5¶m6=value%2F0%2F6&.....¶mN=valueN
Response: 500 Server Error"
in which the request is displayed on a single line, even if it doesn't fit in the visible frame of the report
The text was updated successfully, but these errors were encountered: