Test run execution time is not calculated correctly (playwright-qase-reporter)
complete
Ilya Volkov
complete
Hi everyone!
We've added new property of a test run which will allow you to track how much time your automated run took in fact, if tests were run in parallel.
From now, in a run you will see two values for time spent in a run:
- Total Time: this is what's previously known as "Duration", or in other words, the sum of "Time spent" recorded for all case results in a run.
- Elapsed Time - this is the new property of a run; it will show you the overall runtime of how long the tests took to be executed (so if they were run in parallel, you will see runtime of the parallel execution there, instead of a sum of results' time).
We hope this is a helpful addition - happy testing!
Manjunatha Reddy
Hi Kelzang Dorji,
I’m happy to let you know that our product team is already aware of this issue, and it’s on our list of priorities to address.
We have several improvements related to automated testing planned for this and the upcoming quarters, so we hope to resolve this issue soon.
I'll keep you posted :)
Manjunatha Reddy
planned
Manjunatha Reddy
Hello Kelzang Dorji,
At the moment, the reporter only reflects the results from Playwright. As you correctly pointed out, the execution time displayed is the total of all test durations combined.
While it’s possible add a feature to the reporter to capture this data from the Playwright run, the backend currently calculates the total test duration by simply summing up the individual times spent on each test. And, there's no option to manually modify the Test run's duration currently.
I’ll bring this issue to the team’s attention and keep you updated.
Manjunatha Reddy
under review