and I run pabot --name Windows --suite invalid --runemptysuite tests/. Since no suites exist named invalid, and therefore no tests match the criteria, Pabot launches a robot process with --suite Windows.
In RobotFramework 6, no tests would run because the suite Windows does not exist in the test structure, and robot would exit.
In RF7, the --name option is parsed earlier than the --suite option, causing the top-level suite to be renamed to "Windows" first, and then robot runs all the suites in the virtual "Windows" directory.
I think the correct behavior for when no tests are found but --runemptysuite is specified is for Pabot to pass the --suite option from the Pabot command directly to the robot process without replacement.
Say I have suite structure:
and I run
pabot --name Windows --suite invalid --runemptysuite tests/
. Since no suites exist namedinvalid
, and therefore no tests match the criteria, Pabot launches a robot process with--suite Windows
.In RobotFramework 6, no tests would run because the suite Windows does not exist in the test structure, and robot would exit.
In RF7, the
--name
option is parsed earlier than the--suite
option, causing the top-level suite to be renamed to "Windows" first, and then robot runs all the suites in the virtual "Windows" directory.I think the correct behavior for when no tests are found but
--runemptysuite
is specified is for Pabot to pass the--suite
option from the Pabot command directly to the robot process without replacement.