Skip to content
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

Open
KyleTheScientist opened this issue May 2, 2024 · 0 comments
Open

RF7 > --name option causes ALL suites to run #579

KyleTheScientist opened this issue May 2, 2024 · 0 comments

Comments

@KyleTheScientist
Copy link

KyleTheScientist commented May 2, 2024

Say I have suite structure:

tests/
├──suite_one.robot
└──suite_two.robot

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.

@KyleTheScientist KyleTheScientist changed the title RF7 > --name option causes ALL suites to run RF7 > --runemptysuite option causes ALL suites to run May 2, 2024
@KyleTheScientist KyleTheScientist changed the title RF7 > --runemptysuite option causes ALL suites to run RF7 > --name option causes ALL suites to run May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant