Serenity Report Summary shows the test as failed/error when actually passed on retry about serenity-core

[wakaleo]

I'm not able to reproduce this - both surefire.rerunFailingTestsCount (or failsafe.rerunFailingTestsCount) and max.retries seem to work fine, independently or together. Note that they are totally separate implementations (the surefile.rerunFailingTestsCount property was implemented after the Thucydides one), so probably not a good idea to combine them. Do you have a sample project that reproduces this issue?

[wakaleo]

Could you see if this happens with 1.0.47 and, if so, create a sample project that reproduces the issue?

[mihaiserdean]

I will update to 1.0.47 and delete the surefile.rerunFailingTestsCount property and let you know if I reproduce it.

[afcbpeter]

Hi,

I'm having this issue as well on 1.0.47. The test passes in the Maven Build but Serenity isn't having it.

The faliure I get is this. expected:<[Logout]> but was:<[]> which says to me it's not finding the element, but why would the Maven build pass? the output fail and the Jenkins build show as failed also.

[wakaleo]

Could you provide a sample project that reproduces this issue?

[YamStranger]

@mihaiserdean this issue quite similar to #132. May be next tips will be helpful

• be sure that you are talking about serenity reports (ander serenity output dir). They are builds after gradle reports. Here you can find details configuration. Gradle reports can be rad, but serenity-reports should be green.
• try run example project (I tested it with gradle 2.5). Clone it from git, remove all from serenity.properties (hack, don't use it in real life). And run gradle clean test aggregate. You will find two reports: - fail under build/** and successful under target/serernity/site (default path for serernity reports).

If you will have some additional questions - please ask them

[YamStranger]

Hello @mihaiserdean!

This should be closed under 1.1.22-rc.5.

Please close it, if so