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

Ability to Multi-select tests from web-ui #2304

Closed
gumpcraca opened this issue Feb 23, 2023 · 4 comments
Closed

Ability to Multi-select tests from web-ui #2304

gumpcraca opened this issue Feb 23, 2023 · 4 comments
Labels
feature request stale Issue had no activity. Might still be worth fixing, but dont expect someone else to fix it

Comments

@gumpcraca
Copy link

Is your feature request related to a problem? Please describe.

Occasionally I would like to select one test, then another, or some combination of tests.

Describe the solution you'd like

Ideally the web-ui, when starting a new test, would allow users to multi-select the available tests (based on the tags run at the CLI) This information should be kept in the web-ui and displayed in the Locust Test Report. If possible on the chart tab, it should also show some info maybe on-hover where it currently shows "Run #1" as to what tests were run. If all tests were run, perhaps "All" would be sufficient.

Describe alternatives you've considered

Right now, I kill locust and restart with different tags.

Additional context

Locust is great, thanks for making it! I especially like being able to couple my load testing with my project to share across the dev team :)

@cyberw
Copy link
Collaborator

cyberw commented Feb 23, 2023

Maybe the —class-picker option can be helpful?

@gumpcraca
Copy link
Author

--class-picker is nice but I'd like to choose specific tests

@github-actions
Copy link

github-actions bot commented May 1, 2023

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 10 days.

@github-actions github-actions bot added the stale Issue had no activity. Might still be worth fixing, but dont expect someone else to fix it label May 1, 2023
@github-actions
Copy link

This issue was closed because it has been stalled for 10 days with no activity. This does not necessarily mean that the issue is bad, but it most likely means that nobody is willing to take the time to fix it. If you have found Locust useful, then consider contributing a fix yourself!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request stale Issue had no activity. Might still be worth fixing, but dont expect someone else to fix it
Projects
None yet
Development

No branches or pull requests

2 participants