-
-
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
[Serenity Junit 5 ]: No BaseStepListener has been registered - are you running your test using the Serenity runners? #2790
Comments
hi @bachhavdipak, are you running the tests in parallel? |
No, I am not running the test in parallel mode but trying to do POC for that purpose I have added junit-platform.properties file
|
|
hey @pogodins can you try please with |
@cliviu, thanks for sharing repo! I checked it with Serenity 3.2.4.
|
@pogodins , very strange, I cannot reproduce it in my environment with the following settings
Can you please the log output when running in your environment (exceptions included) ? |
Please find below my console output when running tests from https://github.com/wakaleo/swaglabs-serenity-junit5 with Maven and concurrent parallel methods and classes in JUnit:
As you can see only tests from a class with multiple @test methods are failing. |
thanks, do you also have the stack traces ? |
and your pom.xml please |
pom.xml contents:
|
No additional traces are coming. I assume because of this line: serenity-core/serenity-core/src/main/java/net/thucydides/core/steps/StepEventBus.java Line 163 in c655383
|
ok, thank you, I will take a look to see if I can find a solution |
can you please try to run with |
yes, I hope that is fixed now, at least I could not reproduce it in my environment anymore |
@cliviu, thanks for fixing! I can confirm that it's working fine for me now with Serenity "3.2.6-SNAPSHOT" and the following JUnit config:
|
Great, than maybe we should close the issue for now, right? |
* fix performance problem when choosing the right TestStrategyAdapter * remove unused classes * added support for @DisplayName , improve release notes * delete not used releaseNotes file * JUnit5: clearTestOutcomes at baseStepListener after generating report * JUnit5: clearTestOutcomes at baseStepListener before starting test, fix @CsvSource with text block * fix performance problem when choosing the right TestStrategyAdapter * remove unused classes * added support for @DisplayName , improve release notes * delete not used releaseNotes file * JUnit5: clearTestOutcomes at baseStepListener after generating report * JUnit5: clearTestOutcomes at baseStepListener before starting test, fix @CsvSource with text block * fix performance problem when choosing the right TestStrategyAdapter * remove unused classes * added support for @DisplayName , improve release notes * delete not used releaseNotes file * JUnit5: clearTestOutcomes at baseStepListener after generating report * JUnit5: clearTestOutcomes at baseStepListener before starting test, fix @CsvSource with text block * fix performance problem when choosing the right TestStrategyAdapter * remove unused classes * added support for @DisplayName , improve release notes * delete not used releaseNotes file * JUnit5: clearTestOutcomes at baseStepListener after generating report * JUnit5: clearTestOutcomes at baseStepListener before starting test, fix @CsvSource with text block * fix performance problem when choosing the right TestStrategyAdapter * remove unused classes * added support for @DisplayName , improve release notes * delete not used releaseNotes file * JUnit5: clearTestOutcomes at baseStepListener after generating report * JUnit5: clearTestOutcomes at baseStepListener before starting test, fix @CsvSource with text block * fix performance problem when choosing the right TestStrategyAdapter * remove unused classes * added support for @DisplayName , improve release notes * delete not used releaseNotes file * JUnit5: clearTestOutcomes at baseStepListener after generating report * JUnit5: clearTestOutcomes at baseStepListener before starting test, fix @CsvSource with text block * use @serenitybdd as marker for the JUnit5 Serenity managed tests * removed not used class SerenityBDD * fix junit-parallel merge problems * upgrade to rest-assured 5.0.1 * fix junit5 parallel run issue #2790 * fix switching of report terminology more standard use of "scenarios" and "test cases". Co-authored-by: Liviu Carausu <l.carausu@znt.de> Co-authored-by: John Ferguson Smart <john.smart@wakaleo.com>
[serenityCoreVersion = 3.2.0]
Getting below exception while running Junit 5 api test.
Code:
Error:
The text was updated successfully, but these errors were encountered: