When it comes to stress testing, WebRTC is different. And this is because WebRTC is a peer, not a client server.
What you can check is part of the client server, namely the signaling server and the STUN / TURN server. For this you can easily use JMeter for any web server. For STUN / TURN, just follow the specifications (although if you were using an existing server, I would have left this in the hands of the authors if you do not want to participate in this project too). For an alarm server, it depends on how you create it.
What you can also do with WebRTC is to try testing with limited bandwidth and delay / jitter. This will be more like a smoke test than a download. Doing this automatically is a little trickier. especially if you want to do this with audio / video, not data.
source share