Hey @vishnuprakash9845 I’ve looked into this before as well.
LambdaTest is fantastic when it comes to cross-browser testing and running UI automation with Selenium, Cypress, or Playwright. But when it comes to directly automating SignalR or WebSocket APIs, it doesn’t currently offer built-in support for that level of real-time, event-driven API testing.
For SignalR/WebSocket automation, I’d recommend using tools that are more protocol-focused. For example:
- In Node.js, libraries like
wsorsocket.io-clientlet you connect to a WebSocket endpoint and interact with the server. - In Python, the
websocketsorwebsocket-clientlibraries can help you build custom scripts to send/receive real-time data and validate responses.
That said, if your WebSocket events trigger changes on the frontend (like dynamic UI updates), you can use LambdaTest to validate those end-to-end, especially in combination with your real-time test scripts.
So while LambdaTest can be part of the flow, for actual API-level validation of WebSocket/SignalR data, you’d need to complement it with custom test scripts or API testing tools.
Happy to share sample setups or tools I’ve seen work well!