Be able to provide http and websocket client to strawberry shake

Is your feature request related to a problem?

I am using WebApplicationFactory for integration testing which uses its own in memory http client and I have to register IHttpClientFactory to make strawberry shake to use client from web factory instead of its own client which was not straight forward. I was not able to do the same for web sockets.

The solution you'd like

• Ideally be able to pass both clients to strawberry shake via constructor to cover to most likely scenario by looking through other people's code it seems fixture dependencies are mostly instantiated manually rather than resolved via fixture own DI
• Make strawberry shake play nice with what is described in Integration tests in ASP.NET Core as this is how I ended up using strawberry shake client

Product

Strawberry Shake

Edit:

In the end I was able to provide my own web socket implementation by copy pasting web socket client from HC and hardcoding its values as implementing IWebSocketClient is not something I would be able to do.

Start by tracing how Strawberry Shake constructs its HTTP client and IWebSocketClient, focusing on the constructor and dependency-resolution paths used with WebApplicationFactory. Compare the existing IHttpClientFactory integration with the websocket path, then validate that both supplied clients work in an ASP.NET Core integration-test scenario.