-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RF7 > --name
option causes ALL suites to run
#579
Comments
KyleTheScientist
changed the title
RF7 >
RF7 > May 2, 2024
--name
option causes ALL suites to run--runemptysuite
option causes ALL suites to run
KyleTheScientist
changed the title
RF7 >
RF7 > May 2, 2024
--runemptysuite
option causes ALL suites to run--name
option causes ALL suites to run
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.The text was updated successfully, but these errors were encountered: