-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Display current testscript used #1832
Comments
Good idea! Shouldnt be too difficult to do either. Maybe have a go att doing it yourself? |
@cyberw not sure how that could be done by myself unfortunately. I guess more experienced person on this project could add this quicker. |
I’m sure it would be quicker, but it is unlikely to happen. Particularly the UI is ”you want it, you build it”, as I dont use it myself :) |
is there information how to build locust locally ? or can we simply do pip install . maybe ? not sure, I am not really expert in this area :( |
Clone the repo from github, cd into the folder and run |
#1832 Displaying locustfile and tasks ratio information on index.html
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
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! |
Is your feature request related to a problem? Please describe.
Currently when we start locust ui , there are no hints on the page to find out what will be executed exactly.
Describe the solution you'd like
It would be nice to at least display the current testscript filename that was used to start the command a.k.a -f option value.
If not at least the list of tasks that are going to be executed would be also nice to have.
Describe alternatives you've considered
I have no idea of any possible alternative.
Additional context
Distributed installation with many worker machines and a dedicated master running with UI.
The text was updated successfully, but these errors were encountered: