Hey guys, I guess it's a general question regarding running load test distributedly:
If my designated test plan has some request flows that must happen in specific order, e.g. user login/logout, running in distributed mode might cause problems, for example, if the execution happens like this:
node1: userA log in, generated tokenA1
node2: userA log in, generated tokenA2, invalidated tokenA1
node1: userA log out using tokenA1, will fail because tokenA1 is invalidated
Does locust handle such cases where requests have dependencies and order? Thanks
Hey friends! I'm currently writing a traffic replay framework, using locust as the base.
My current issue is this:
I want to be able to spawn locust workers and have them make requests asynchronously, and then report back to master, right? But! I need them to NOT play the same traffic. Essentially, I need a centralized entity to pub/sub events to tell my workers to make the requests.
I thought the obvious choice there was to have the locust master manage the messaging for sending the requests.
So I have two questions:
helm install stable/redisisn't a huge deal.
uribut not both