[Feature]: Add support for Robot Framework --parser in pabot

[Qwazertyx]

What problem does this solve?

pabot does not expose the --parser option for custom test data parsers cleanly for parallel execution.

Proposed solution

Pass --parser through to Robot subprocesses, support multiple values, and keep it out of rebot options.
PR #723

[joonaskuisma]

Hi! If I understood the situation correctly, is the problem that the --parser option is currently being passed to the rebot command as well? Or do you think it’s not working as intended? Could you clarify the issue in the issue tracker with an example?

I took a quick look at the PR, and the problem there is that pabot_args is reserved for pabot’s own options. All so-called “unknown” options (i.e., Robot Framework’s own options) are passed as-is to the subprocesses.

[Qwazertyx]

yes unknown Robot options should be forwarded as-is, but custom parsers were not passed during suite discovery

I found one extra issue in discovery: with custom datasource extensions, suite discovery wasn’t passing custom parsers to TestSuiteBuilder, so Pabot failed early with “contains no tests”.

python -m robot --dryrun --parser demo_parser.DemoParser --outputdir results_robot_ok sample.demo
-> 2 tests, 2 passed, 0 failed

python -m pabot.pabot --dryrun --command python -m robot --end-command --parser demo_parser.DemoParser --outputdir results_pabot_ok sample.demo
-> works fine after the patch