Skip to content
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

Attachment name for RestAssured responses is set once and is reused across all subsequent responses #678

Closed
serzhshakur opened this issue Nov 8, 2021 · 0 comments · Fixed by #679

Comments

@serzhshakur
Copy link
Contributor

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).

allure_bug_repot

To Reproduce
Just reuse the same instance of AllureRestAssured across multiple HTTP requests.
From the picture above:

  1. Attachment name is set to HTTP/1.1 302 Found when response for the first request is received;
  2. 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant