New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Combining DataDriver and non-DataDriver tests repeats non-DataDriver tests (PROCESS) times #465

Closed

burrk opened this issue Mar 21, 2022 · 1 comment

burrk commented Mar 21, 2022 •

edited

Loading

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=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

All testnames are unique.

The text was updated successfully, but these errors were encountered:

Author

burrk commented Mar 21, 2022

Fixed with https://github.com/mkorpela/pabot/releases/tag/2.5.1

burrk closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment