-
Notifications
You must be signed in to change notification settings - Fork 19
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
[@SerenityWithCucumber] Report Portal creates redundant launches for multi module project #63
Comments
jUnit is configured to run tests in parallel using JVM forking.
So tests on each submodule run on a different JVMs. But for now integration controls RP communication client on one JVM level, so practically with your example several client created, as a result you got several launches in RP. Potentially is it possible to avoid it with cross JVM communication, but efforts to do it is too high comparing to this use case rarity. |
Hello, Do you have any plans to fix the issue? We faced with the same problem recently. Thanks. |
@slavamarkovski |
@Invictum sorry for pushing but do you have any rough ETA for this issue? |
I made a small investigation and actually it is more complex than expected. It requires cross JVM communication even with merge approach. As for estimates: It depends on my free time, but I will try to implement it in a few weeks. |
Implemented. Will be available on 1.4.2+ @slavamarkovski |
#63: Implemented launches merge for multi-module project
On running tests in multimodule test-automation-framework, Report Portal creates a separate launch for each module. It generates redundant launches for modules which don't have any tests with the specified tag.
Would it be possible to keep all tests results in one launch even though tests are defined in different maven modules?
The project simple-multimodule-project.zip:
Execute the following command to reproduce the issue:
mvn clean verify -Dcucumber.options="--tags '@API'"
The text was updated successfully, but these errors were encountered: