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
Describe the bug
When using singleton instance of AllureRestAssured filter, attachment name is set once and the same name is then reused across all subsequent responses (see picture).
To Reproduce
Just reuse the same instance of AllureRestAssured across multiple HTTP requests.
From the picture above:
Attachment name is set to HTTP/1.1 302 Found when response for the first request is received;
Attachment name is set to HTTP/1.1 302 Found for 2nd all subsequent requests which is incorrect. Should be HTTP/1.1 200 OK instead
Expected behavior
Attachment name should be correctly set for the 1st and all subsequent RestAssured responses
Additional context
PR will folow
The text was updated successfully, but these errors were encountered:
Describe the bug
When using singleton instance of AllureRestAssured filter, attachment name is set once and the same name is then reused across all subsequent responses (see picture).
To Reproduce
Just reuse the same instance of AllureRestAssured across multiple HTTP requests.
From the picture above:
HTTP/1.1 302 Found
when response for the first request is received;HTTP/1.1 302 Found
for 2nd all subsequent requests which is incorrect. Should beHTTP/1.1 200 OK
insteadExpected behavior
Attachment name should be correctly set for the 1st and all subsequent RestAssured responses
Additional context
PR will folow
The text was updated successfully, but these errors were encountered: