By joezimjs
via joezimjs.com
Submitted: Feb 08 2013 / 11:16
In my last article, where I talked about unit testing Socket.IO with Jasmine, there was a point where I mentioned that I needed to use timeouts that were a second and a half when doing the asynchronous connecting and disconnecting from the Socket.IO server. It was working just fine with 750 millisecond timeouts on Firefox, but when I tested it in Chrome, timeouts were being reached and the specs were failing. Let’s see if we can get to the bottom of this and figure out why Chrome failed so hard here.
Tweet
SaveShareSend
Tags: frameworks, javascript, tools
Add your comment
