Repository navigation

🐞: Spock fixture methods not added to Allure report correctly #967

Closed

Labels

opened

on Oct 13, 2023

What happened?

Project https://github.com/karltiirik/spock-restassured-allure/releases/tag/fixture-methods-issue
2 tests in a single file, all fixture methods present:
Run tests ./gradlew clean test
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

I agree to follow this project's Code of Conduct

karltiirik
added
triage

pr:bugSomething isn't working
on Oct 13, 2023
AlenaKaraliova commented on Mar 13, 2025
AlenaKaraliova
on Mar 13, 2025
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.
baev
added the
Bug
issue type on Jul 10, 2026
baev
removed
pr:bugSomething isn't working
on Jul 10, 2026
baev
closed this as completedin #1339 on Jul 23, 2026
yurkki
added a commit that references this issue on Jul 29, 2026
improve spock block and fixture reporting (fixes allure-framework#965, …
368e014

to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

Labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests