Skip to content
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 Report - Total test durection wrong - is not the sum of all steps #3435

Open
AndreasScharfCPB opened this issue Apr 12, 2024 · 5 comments

Comments

@AndreasScharfCPB
Copy link

What happened?

Actually I was looking at the results.csv and the reported duration there seems to low. So I was looking at the serenity report an it shows a total duration that is too low and I couldn't figure out how that was happening. Seems random

In my serenity report I see the steps and the total duration and it does not match at all. Nothing runs in parallel. Not the tests not the steps.

What did you expect to happen?

Total Test duration = Sum of all steps or similar

Serenity BDD version

4.1.3

JDK version

17

Execution environment

Linux Server, Jenkins, maven build

How to reproduce the bug.

Apparently happening in all of my tests
image
image

How can we make it happen?

Add it to the Serenity BDD backlog and wait for a volunteer to pick it up

@wakaleo
Copy link
Member

wakaleo commented Apr 12, 2024

I'm not able to reproduce this.

@AndreasScharfCPB
Copy link
Author

Hmm..

I am using Java 17 and maven 3.8.6
mvn clean verify serenity:aggregate -Dmaven.test.failure.ignore=true -Dheadless.mode=true

I will try to compile a small working example

@Moncada25
Copy link

This has already been reported before, I see that it continues to fail :(
#3315

@wakaleo
Copy link
Member

wakaleo commented Apr 21, 2024

This has already been reported before, I see that it continues to fail :( #3315

@Moncada25 There is no SLA on open source - if this issue is important to you, you can always (a) investigate and propose a PR to fix the issue, or (b) subscribe to a commercial support contract so you can prioritise the issue.

@AndreasScharfCPB
Copy link
Author

After upgrading to serenity 4.1.10 it seems to work again.
So for me there are no further actions needed. Thanks for your support!
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants