Incorrect timing of the test

ozontech / allure-go

Complete Allure provider in Go which doesn't overload the interface usage

https://t.me/allure_go_chat

Apache License 2.0

317 stars 34 forks source link

Incorrect timing of the test #41

Open ImOsMa opened 1 year ago

ImOsMa commented 1 year ago

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:

Run tests with allure-steps

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

Screenshots

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

arpogodin commented 1 year ago

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