pabot first tests batch delay start

[puandr]

Hello,

I have a test suite with >200 tests, running 30 tests in parallel with pabot, no problem, BUT except for the starting batch, as all tests have to get information from an old legacy source that's unable to handle all those requests, so like 20 of 30 tests are starting with incomplete data and are failing on different stages. Further, there's no problem, each test gets its starting data (and we automatically rerun failing tests anyway).
My suggestion is to add an option, so the test in the first batch will start with a fixed or random delay.

Regards,
Andrei

[mluyun]

+1 to this.

In my current project we are using webdriver manager. we are only running about 20-40 test cases in 5 parallel threads, the first 5 test cases usually fail when the webdriver download is not yet finished but the test using pabot already started the execution.
A workaround we did was to invoke the webdriver manager first to download the webdriver and then start the test execution using pabot.

[joonaskuisma]

Hi @puandr and @mluyun !

I've already created the #SLEEP keyword, which solves this issue. However, it hasn't been merged into the main branch yet and is therefore not available in the latest version.

If you're interested, you can find it and leave comments on the related issue #592, which links to the branch where I've implemented it.

Cheers! 🚀

[joonaskuisma]

This is implemented in 4.2.0 version of Pabot.

[puandr]

I'm not in that project anymore, but I'll communicate this information to them. Thank you!