improvement: It would be nice if MFTF report the total amount of seconds spent in wait

[tmotyl]

The full MFTF takes really long time.
Much of this time is spend in waiting.
In order to be able to see how big the problem is exactly, it would be very beneficial to count total time spent by tests in waiting for somethin or sleeping.

[tomreece]

Hi @tmotyl thank you for your suggestion.

I don't think there will be an easy way for us to measure the total time spent waiting during test execution.

One thing you can do is search your test codebase for <wait (with a space after it).
This will show you all explicit waits in your test code base. We advise against using explicit waits but sometimes it is unavoidable. But at least searching this will point out some problems that should be fixed if possible.

Let's say we could implement this feature easily, in what ways would you make use of it? What will you do with the result? That part is not clear to me.

[okolesnyk]

Hi @tmotyl
We will close this issue and hope you've been able to solve the issue. I hope that Tom Reeces suggestion helped.
Also, I'd like to suggest looking into Allure reports because there you can see how much time each specific action took.

[tmotyl]

The goal of course is to be able to see how much time is spent in explicite wait - thus whether its a real bottleneck and is worth refactoring tests to avoid wait.