Let me try to understand it.
Lets assume we have three suites and each suite has tests, suite2 is datadriven:
templatetest (dd with 10 testcases in file)
now i call
pabot --testlevelsplit --processes 2 .
how would the pabot queue look like?
And when the
start_suite(suite) of DataDriver Listener gets called, Pabot assumes that this suite has one test, that is called
But with DataDriver
templatetest is deleted and
test2.10 is added to the suite.
i could also add 2 time 5 tests instead of 10 times one test. I don´t know if this is possible.
But if DataDriver knows, that pabot has max 2 threads, it would be much better performance to just execute all 10 testcases in two parts, instead of ten.
DataDriver has already the possibility to get DYNAMICTESTS as a list of testnames or a string pipe seperated.
So if i would add to the queue two Suites like this:
What happens with the current test suite, that is executed at the moment?
What would happen if i delete the test, after putting the both suites to the queue?
And how does DataDriver knows, that this is the “first” call of this suite?
Can you explain a bit more, when the pabot queue looks like what?