-
Notifications
You must be signed in to change notification settings - Fork 514
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
feat(artillery): add ability to specify scenario to run by name #2184
feat(artillery): add ability to specify scenario to run by name #2184
Conversation
…io-by-name-in-artillery-cli
@hassy made the changes we discussed (expose to Lambda, and error instead of logging). I went with erroring from within here a5604ae (i.e. worker level), rather than earlier in the script. The reason is that this way it's not dependant on Screenshots of errors:Scenario Not FoundMultiple Scenarios Found |
I've made this work with Lambda now, and tested it 👍. Both happy path and errors work now. Fargate support will require updating platform-fargate, which I'll do next. |
Why
Originally requested here #1929, this is a useful feature for people who are saving multiple scenarios in the same file. Especially useful once you start having complex scenarios with weights, but still want the ability to run them individually on demand, a requirement I've had myself in the past.
Note: CLI flag name (--name
) could be changed to something else, like--byName
. Please suggest something else if you think it makes more sense.Note: Flag name is now --scenario-name after some internal discussions. Please make other suggestions if other ideas pop up.