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

Display current testscript used #1832

Closed
tyge68 opened this issue Jul 30, 2021 · 8 comments
Closed

Display current testscript used #1832

tyge68 opened this issue Jul 30, 2021 · 8 comments
Labels
feature request stale Issue had no activity. Might still be worth fixing, but dont expect someone else to fix it

Comments

@tyge68
Copy link
Contributor

tyge68 commented Jul 30, 2021

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.

@cyberw
Copy link
Collaborator

cyberw commented Jul 30, 2021

Good idea! Shouldnt be too difficult to do either. Maybe have a go att doing it yourself?

@tyge68
Copy link
Contributor Author

tyge68 commented Jul 30, 2021

@cyberw not sure how that could be done by myself unfortunately. I guess more experienced person on this project could add this quicker.

@cyberw
Copy link
Collaborator

cyberw commented Jul 30, 2021

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 :)

@tyge68
Copy link
Contributor Author

tyge68 commented Jul 30, 2021

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 :(

@cyberw
Copy link
Collaborator

cyberw commented Jul 30, 2021

Clone the repo from github, cd into the folder and run
pip3 install -e .

@tyge68
Copy link
Contributor Author

tyge68 commented Jul 30, 2021

@cyberw thanks a lot, I managed to do something, you can check my draft PR on #1833

tyge68 added a commit to tyge68/locust that referenced this issue Aug 11, 2021
tyge68 added a commit to tyge68/locust that referenced this issue Aug 31, 2021
tyge68 added a commit to tyge68/locust that referenced this issue Aug 31, 2021
tyge68 added a commit to tyge68/locust that referenced this issue Aug 31, 2021
tyge68 added a commit to tyge68/locust that referenced this issue Aug 31, 2021
tyge68 added a commit to tyge68/locust that referenced this issue Sep 1, 2021
tyge68 added a commit to tyge68/locust that referenced this issue Sep 1, 2021
tyge68 added a commit to tyge68/locust that referenced this issue Sep 1, 2021
tyge68 added a commit to tyge68/locust that referenced this issue Sep 1, 2021
tyge68 added a commit to tyge68/locust that referenced this issue Sep 1, 2021
cyberw added a commit that referenced this issue Sep 1, 2021
#1832 Displaying locustfile and tasks ratio information on index.html
@github-actions
Copy link

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.

@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 Sep 29, 2021
@github-actions
Copy link

github-actions bot commented Oct 9, 2021

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!

@github-actions github-actions bot closed this as completed Oct 9, 2021
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