Alexander Rose

Hi, I agree the current setup for integration-testing against a webserver setup is not elegant. Currently it's spinning up an actual webserver on a free port on the testserver. I'd...

I'm actually hoping for improved stability on the integration test through this, too (see #161). 😉

Thanks for your work, I'll try to review this over the weekend...

I'm really sorry, but I didn't get around to this yet... It's still on my To-Do list though.

This library sends each GraphQL request as a POST request (see [here](https://github.com/graphql-dotnet/graphql-client/blob/10c22365ebce413ae3c4249518fecbfd415af575/src/GraphQL.Client/GraphQLHttpRequest.cs#L39)). You can create your own request class (which inherits from `GraphQLHttpRequest`) and override the `ToHttpRequestMessage` to change that...

Hi, I've never experienced something like this using that library. What type of server are u using? How did you try to test this using Playground? Does Playground use a...

Open the devtools of your browser and switch to the network analyzer before starting the subscriptions... If you see a new websocket connection opening up on each subscription then those...

To replicate that you would have to use two instances of `GraphQLHttpClient`...

@Willbill360 IMO this is a bad workaround... I added the "crossinterference" test locally, and it shows no issues. I really think this is an issue with your server (graphql-yoga) which...

Thanks for your investigations! Care to post a complete example? The creation of the GraphQLHttpClient was missing from your fist post. Calling `client.InitializeWebsocketConnection()` shouldn't be necessary since that's automatically invoked...