Current time: 09-21-2019, 02:07 AM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 1 Vote(s) - 4 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Websocket
07-19-2016, 05:34 PM
Post: #4
RE: Websocket
(04-27-2016 01:52 AM)shawn.siefkas@meredith.com Wrote:  What if the socket isn't necessarily idle by design (i.e. push based messaging)? This seems to block test completion in some of our use cases. Is there a way to blacklist or ignore web socket connections during a test?

Sorry to bump an old thread but it seems relevant.

Currently we are facing the same issue. The test does not finish because of the open socket. Is it possible to finish the test manually? I read something about
Code:
if( window.webpagetest )
    window.webpagetest.done();
which we could inject to our javascript, but that just seems to work in IE. Any help is highly appreciated.

Thanks!
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
Websocket - milkanast - 09-29-2014, 05:46 PM
RE: Websocket - pmeenan - 10-01-2014, 11:04 PM
RE: Websocket - shawn.siefkas@meredith.com - 04-27-2016, 01:52 AM
RE: Websocket - krauer - 07-19-2016 05:34 PM

Forum Jump:


User(s) browsing this thread: 1 Guest(s)