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

The teardown step is printed in testbody #2714

Open
1 task done
abincoding999 opened this issue Sep 4, 2024 · 1 comment
Open
1 task done

The teardown step is printed in testbody #2714

abincoding999 opened this issue Sep 4, 2024 · 1 comment
Labels
type:bug Something isn't working

Comments

@abincoding999
Copy link

abincoding999 commented Sep 4, 2024

The teardown/Hook step is printed in testbody

image
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

  • I agree to follow this project's Code of Conduct
@abincoding999 abincoding999 added triage type:bug Something isn't working labels Sep 4, 2024
@baev
Copy link
Member

baev commented Oct 2, 2024

After step hooks are executed during the test, Allure displays it correctly.

You can use Allure Lifecycle API to "fix" the report, e.g. remove the logging for after-step hooks or rename it to something more meaningful.

@baev baev removed the triage label Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants