Proposed testsuite only catches issue 737 regression in https mode. Also, it tests h2, because native chromium is involved.
I'll check whether VTC is able to catch issue 737. As for proposed test suite, it is really heavy to run on CI. But it might be used as release quality gate On Wed, Oct 20, 2021, 9:50 AM Amaury Denoyelle <adenoye...@haproxy.com> wrote: > On Wed, Oct 20, 2021 at 09:59:59AM +0500, Илья Шипицин wrote: > > Hello, > > I've found a way how to test websockets automatically. > > this approach is able to catch > https://github.com/haproxy/haproxy/issues/737 > > > > the idea is to place haproxy between browser and kestrel in SignalR > tests ( > > https://github.com/dotnet/aspnetcore/tree/main/src/SignalR ) > > test takes 3 hours on my low end laptop. > > I collected all required parts in > > https://github.com/chipitsine/haproxy-signalr-tests > > also, I checked current maintained branches, no issues (last issue was > > fixed in issue 737). > > Hi, > > I did not look precisely at your testsuite, but note that now we have > some websockets related VTC regtests. Of course, this does only test the > tunnel establishment without websocket data exchange, but it's still a > good start. Also this will be soon extended with a new test to better > handle h2 websocket. > > Regards, > > -- > Amaury Denoyelle >
