Using custom datareader with pabot tests are not executed in parallel about robotframework-datadriver HOT 5 CLOSED

As DataDriver - pabot binding is a custom thing I would start from here. Pabot assumes that DataDriver does few tricks and maybe this does not happen when using custom datareader.

from robotframework-datadriver.

That is funny, because everything which belongs to DYNAMICTESTS is in DataDriver class and not in the readers.

I will check this...

from robotframework-datadriver.

i really cant reproduce you situation.
I think the import from test.datareader.simplemodule import aSillyFunction just do not work and DataDriver then runs into an exception, because the custom_reader can not been imported at all.

i would assume that this is not a bug in DataDriver, it is just a wrong import...

When this happens, because DataDriver does absolutely nothing, Pabot does not know that there are DYNAMICTESTs. so Pabot create a pabotsuitenames with just the Suite in it and not Test Cases.
This leads to the situation, that on the next run, when pabotsuitenames already exists, it executes only the Suite and does not execute the tests in parallel.

BUT: it found a "bug":
the import of custom readers can be a relative path, but it must be relative to the folder where robot is executed. This is somehow strange. It is now also possible to use a relative path to *.robot file. In your case it was the same, because you executed robot from the same directory.

it is available in 0.4.0b1
pip install -U --pre robotframework-datadriver

Ps: If you think this is not the case (with the wrong import) please upload a project where we can reproduce it. Because i wasn’t able to get this import running at all.

from robotframework-datadriver.

Thank-you. I have attached an example.
TestPabotCustomDataReader.zip

There is something strange going on with the Python path though. I was testing the example which I uploaded changing the import back and forth; and I was getting the expected results. Just before I went to zip, I removed all the generated files and some hidden directories and then ran again: only the from simplemodule import aSillyFunction import will work now. Using the import from test.datareader.simplemodule import aSillyFunction is causing the test to not even execute due to the module test.datareader not being found on the Python path. The stack trace in log.html though clearly shows the absolute path to the py3 directory showing up. I sent the example to a colleague. The example runs for her but test cases do not get parallelized (as expected with the import).

from robotframework-datadriver.

i close it due to completely new implementation with Pabot will come soon

from robotframework-datadriver.