search

mkorpela / pabot

Parallel executor for Robot Framework test cases.
https://pabot.org
Apache License 2.0
475 stars 152 forks source link

Pabot is not handling error cause by the --command option #570

Open RasmusGOlsen opened 8 months ago

RasmusGOlsen commented 8 months ago

If calling Pabot with the option --command mycmd robot --end-command and mycmd fails, i.e. Robot fails to start the test case, Pabot will not handle this. I would expect the XML to be generated with the reason that the test case failed to start.

# file: example.robot
*** Test Cases ***
Test A
    Log    Running ${TEST NAME}

Test B
    Log    Running ${TEST NAME}
$ pabot --splitleveltest --command mycmd robot --end-command example.robot

Storing .pabotsuitenames file
2024-02-22 12:07:39.041035 [PID:18335] [0] [ID:0] EXECUTING Example.Test A
2024-02-22 12:07:39.041338 [PID:18336] [1] [ID:1] EXECUTING Example.Test B
2024-02-22 12:07:39.241447 [PID:18335] [0] [ID:0] FAILED Example.Test A
2024-02-22 12:07:39.241871 [PID:18336] [1] [ID:1] FAILED Example.Test B
[ ERROR ] Reading XML source '' failed: No such file or directory

Try --help for usage information.
WARN: No output files in "./pabot_results"
0 tests, 0 passed, 0 failed, 0 skipped.
===================================================
Output:  
Total testing: 0.40 seconds
Elapsed time:  0.31 seconds