For example, using optimize_pabot=Atomic in the Pabot_Test.robot code:
pabot --testlevelsplit --pabotlib .\Test\Pabot_Test.robot Total testing: 2 minutes 17.70 seconds
pabot --testlevelsplit --pabotlib .\Test\invalid_login.robot Total testing: 19.99 seconds
pabot --testlevelsplit --pabotlib .\Test\invalid_login.robot .\Test\Pabot_Test.robot Total testing: 7 minutes 55.60 seconds The 25 DataDriver tests are only run once, while the 7 “Invalid Login” tests are run 26 times.
I used a clean Python 3.8 venv, and installed
robotframework 4.1.3
robotframework-datadriver 1.6.0
robotframework-pabot 2.3.1
The Library line in Pabot_Test.robot was:
Library DataDriver MostSearched.xlsx sheet_name=Lapas1 optimize_pabot=Atomic
burrk
commented
2 years ago
Hi,
Originally from https://forum.robotframework.org/t/data-driven-in-parallel-2-each-data-driven-tc-takes-other-tcs-for-a-ride/3429 and was discussed with @mkorpela in https://robotframework.slack.com/archives/C7HKR2L6L/p1647471796103679 where he was able to reproduce it.
Data-Driven_in_Parallel_2.zip
For example, using
optimize_pabot=Atomicin thePabot_Test.robotcode:pabot --testlevelsplit --pabotlib .\Test\Pabot_Test.robotTotal testing: 2 minutes 17.70 seconds
pabot --testlevelsplit --pabotlib .\Test\invalid_login.robotTotal testing: 19.99 seconds
pabot --testlevelsplit --pabotlib .\Test\invalid_login.robot .\Test\Pabot_Test.robotTotal testing: 7 minutes 55.60 seconds
The 25 DataDriver tests are only run once, while the 7 “Invalid Login” tests are run 26 times.
I used a clean Python 3.8 venv, and installed
The Library line in
Pabot_Test.robotwas:Library DataDriver MostSearched.xlsx sheet_name=Lapas1 optimize_pabot=AtomicAll testnames are unique.