-
-
Notifications
You must be signed in to change notification settings - Fork 513
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
Duplicate logging when running with cucumber #3372
Comments
This can happen if you have defined Cucumber reporting plugins in more than one place (e.g. in the annotations and in the junit-platform.properties file). It's a Cucumber configuration issue, unrelated to Serenity. |
@wakaleo Thanks for answering. I don't have any "junit-platform.properties" within my project. Instead I have removed "cucumber.properties" located under resources but this could not solved the problem. Could you please point me to the cucumber configuration issue? I have performed some test runs with different annotations but it looks like a serenity issue to me: SerenityReporterParallel + pretty
SerenityReporterParallel
pretty
The serenity logging always starts when the test execution has been finished. |
It's not a Serenity issue (Serenity doesn't log the Cucumber steps). I'd have to see your project, but I presume there must be somewhere else where the Cucumber logs are being configured? |
@wakaleo I could solving the issue by replacing SerenityReporterParallel with SerenityReporter and removing pretty printer:
Thus, in my humble opinion it was caused by Serenity's parallel reporter. Closing this issue. |
What happened?
When running tests with IntelliJ or Gradle runner the logging is kind of duplicated. The above logging block is written when the test is actually running whereas the below logging block is written after the test has been finished. The duplicate log entries were written every 0.5 seconds but there was no chromedriver running anymore.
What did you expect to happen?
There should only one logging of test execution. When the test has passed the logging should be finished, too.
Serenity BDD version
4.0.15
JDK version
11.0.21
Execution environment
macOS Ventura 13.6.3
Chrome 120.0.6099.216
How to reproduce the bug.
Run a test class configured like below with Gradle or IntelliJ runner and verify the logging.
How can we make it happen?
Add it to the Serenity BDD backlog and wait for a volunteer to pick it up
The text was updated successfully, but these errors were encountered: