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

Incorrect timing of the test #41

Open
ImOsMa opened this issue Nov 22, 2022 · 1 comment
Open

Incorrect timing of the test #41

ImOsMa opened this issue Nov 22, 2022 · 1 comment

Comments

@ImOsMa
Copy link

ImOsMa commented Nov 22, 2022

Describe the bug
In allure report every step of the test has execution time, and if we sum every step time, it will not be equal to duration

To Reproduce
Steps to reproduce the behavior:

  1. Run tests with allure-steps

Expected behavior
Summ of the execution time of steps is equal to duration

Screenshots
Снимок экрана 2022-11-22 в 12 20 33

Additional context
As you can see duration != summ of the time of steps

@arpogodin
Copy link

arpogodin commented Jun 8, 2023

Also run into this issue. In my case it appears that the time reported in Duration is the time passed starting from the suite execution up to a certain tests completion. The number of tests which are being run in parallel is limited by -parallel option (by default it is set to GOMAXPROC variable value) So some of the tests are waiting completion of another tests, so the overall time in the test report increases.

fixed by explicitly setting -parallel flag to 100 when running the tests

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

2 participants