Skip to content

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

@serzhshakur

Description

@serzhshakur

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions