allure-framework / allure-framework/allure2
The teardown step is printed in testbody
- Dominant language
- HTML
- Stars
- 5.5k
- Forks
- 782
- Avg merge
- 2d 33m
- Merged PRs (30d)
- 16
Description
### The teardown/Hook step is printed in testbody

allure-cucumber7-jvm = 2.24.0 it came in the teardown section but in allure-cucumber7-jvm = 2.27.0 onwards it is coming in the testbody.
### Steps to Reproduce
1. create a test and take screenshot after every step
2. create allure report for 2.27.0 and view it
### Expected Behaviour
hook steps should be in teardown
### Screenshots or Additional Context
_No response_
### What Language are you using?
Java
### What Framework/Allure Integration you are using?
allure-cucumber7-jvm
### What version of Allure Integration you are using?
2.27.0
### What version of Allure Report you are using?
2.27.0
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct
Contributor guide
Research direction
Reproduce the report with allure-cucumber7-jvm 2.27.0 using a screenshot after every step, then compare it with version 2.24.0. Inspect where the hook step appears in the generated report and confirm the fix by verifying that hook steps are shown in teardown rather than testbody.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100