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

Confusing order of test body elements #430

Open
1 of 2 tasks
dr29bart opened this issue Mar 9, 2020 · 0 comments · May be fixed by #1021
Open
1 of 2 tasks

Confusing order of test body elements #430

dr29bart opened this issue Mar 9, 2020 · 0 comments · May be fixed by #1021

Comments

@dr29bart
Copy link
Contributor

dr29bart commented Mar 9, 2020

I'm submitting a ...

  • bug report
  • feature request

What is the current behavior?

Rest-assured request/response attachments are in the end of the body:
image

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

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);
    }
}

What is the expected behavior?

Rest-assured request/response attachments are in order according to test events:
image

What is the motivation / use case for changing the behavior?

Make the report more straightforward

Please tell us about your environment:

Allure version 2.13.2
Test framework [email protected]
Allure integration [email protected]
Allure integration [email protected]
Allure integration [email protected]
Generate report using [email protected]

Other information

N/A

@baev baev linked a pull request Mar 19, 2024 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant