🐞: Spock fixture methods not added to Allure report correctly

[karltiirik]

What happened?

1. Project https://github.com/karltiirik/spock-restassured-allure/releases/tag/fixture-methods-issue
2. 2 tests in a single file, all fixture methods present:
3. Run tests ./gradlew clean test
4. Generate report ./gradlew allureServe Expected: both tests have setup & cleanup, 1 test has setup spec & cleanup spec (the one that ran first). Actual: both tests have setup spec & cleanup spec, 1 test has setup & cleanup

So the logic in the report is the opposite of the Spock framework logic.

What Allure Integration are you using?

allure-spock2

What version of Allure Integration you are using?

2.23.0

What version of Allure Report you are using?

2.23.0

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[AlenaKaraliova]

Hello! Is there any fix planned in near time? Let me propose changes:

• we can leave setup/cleanup specs current behavior as is, because it is convenient to observe full report related to a test, including these spec fixtures;
• for setup and cleanup - the issue is that we are creating interceptors for each of such fixtures, then the containers have same UUID for every test, thus they are started, closed and overridden every test and only the last ones remain; my suggestion is to generate new container UUID during each setup/cleanup fixture invocation.