The current limitation of only supporting HTTP(S) traffic significantly impacts the ability to test applications that utilize SignalR and WebSocket transport. This is not just an issue for Blazor Server applications, but affects any .NET application leveraging SignalR, which is increasingly common in modern web development.

While we have attempted workarounds, such as capturing WebSocket traffic using Fiddler, these solutions do not yield the expected results within Test Studio. The inability to accurately simulate WebSocket communication during load testing compromises the reliability of our performance assessments.

Adding WebSocket support would greatly enhance the functionality of Test Studio and better serve the needs of developers working with modern real-time applications.