We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Rest-assured request/response attachments are in the end of the body:
import io.qameta.allure.restassured.AllureRestAssured; import io.restassured.RestAssured; import org.testng.annotations.Test; import static org.assertj.core.api.Assertions.assertThat; public class T { @Test public static void testa() { RestAssured.replaceFiltersWith(new AllureRestAssured()); assertThat(1).isGreaterThan(0); RestAssured.given().get("https://google.com"); assertThat(5).isGreaterThan(3); } }
Rest-assured request/response attachments are in order according to test events:
Make the report more straightforward
N/A
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
I'm submitting a ...
What is the current behavior?
Rest-assured request/response attachments are in the end of the body:
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the expected behavior?
Rest-assured request/response attachments are in order according to test events:
What is the motivation / use case for changing the behavior?
Make the report more straightforward
Please tell us about your environment:
Other information
N/A
The text was updated successfully, but these errors were encountered: