Skip to content

Issues using locust-wms-load-test #4

@samodadela

Description

@samodadela

Hello,
I tried to run the WMS test... at first it looked promising.

However I found the following problems:

  • locust-wms seems to store it's setting somewhere in the browser (cookies or something)... and once you enter the initial parameters, you can not change them anymore (even closing the browser does not work). It accepts the info but the tests do not start. I had limited success with it by clearing browser data - but event that does not work always.
  • LOG_VERBOSE=1 does not seem to do anything...
  • it seems that the test is requesting GetCapabilities as html instead of xml
# docker run --rm -i -t -p 8089:8089 \
       --env LOG_VERBOSE=1 \
       eduardrosert/locust-wms-test
[2023-12-06 12:16:09,675] 121eb5b3bb1a/INFO/locust.main: Starting web interface at http://0.0.0.0:8089 (accepting connections from all network interfaces)
[2023-12-06 12:16:09,682] 121eb5b3bb1a/INFO/locust.main: Starting Locust 2.2.3
[2023-12-06 12:16:29,460] 121eb5b3bb1a/INFO/locust.runners: Ramping to 100 users at a rate of 10.00 per second
Request successful: https://gis.xxx.com/geoserver/wms?request=GetCapabilities&service=wms&version=1.3.0

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions