Locust Scripting: Seeking Best Practice for Web Applications with WebSockets Calls

[Vignesh-332]

Hello everyone,

I'm currently working on load testing a web application that heavily utilizes WebSocket communication. I'm looking for suggestions on the optimal scripting approach for this scenario using Locust.

Here's a breakdown of the user flow:

1. Launch Application URL
2. Enter User ID and Password
3. Application Home Page Loads (This is where the WebSocket connection is established, and all subsequent client-server communication/ further user navigations occurs via this connection through WebSocket calls.)

My current script approach involves using 'HttpUser' for standard web requests (e.g., login, initial page load). For the WebSocket interactions, I'm integrating the 'SocketloUser' (WebSocket plugin) within the same Locust script. My goal is to handle all WebSocket messages triggered by various user navigations through this single script (Web requests + Web Socket calls).

Could you please review this approach and let me know if there are any better or more recommended ways to handle this type of mixed HTTP/WebSocket application load testing in Locust?

Thank you in advance for your insights!

[cyberw]

Hi @Vignesh-332 !

On reading your question I realized we dont properly support this scenario, but I've made some adjustments. Check the example here and let me know if it would work for you. #3211