Console Logging delayed after whole test run

[jacob-wieland-gematik]

What happened?

When starting a test suite, the test-case boundaries banners (started, passed) as well as the test step descriptions are delayed until the whole test run (all test cases) is finished.

This happened after upgrading to using SerenityReporterParallel and using serenity 4.2.11. I am not sure which of the 2 changes is to blame.

While debugging another issue, I perceived that the console logger is only triggered when doing replay of events. Maybe that is the reason.

What did you expect to happen?

The events should be logged to the console when they happen, thus being properly interspersed with other events being logged by other parts of the test system during the test steps.

Also the started, passed etc. events should frame the logs that happen between them, so they can be properly associated.

Serenity BDD version

4.2.11

JDK version

17

Execution environment

No response

How to reproduce the bug.

Should be reproducible with any feature file with at least 2 scenarios or scenario outlines.

How can we make it happen?

Hire the Serenity BDD team

[jacob-wieland-gematik]

Opened #3606 to fix this.

[jacob-wieland-gematik]

If the proposed solution is rejected as default behaviour, maybe it would be possible to at least have an option to have live-logging.

As it is, the logging is completely useless and confusing when played after the actual execution.