Feature proposal: disconnect tolerance

I'm using karma in a continuous integration script on travis and the browsers are launched on browserstack.
Because the connection between browserstack and the travis vm are done through a tunnel, I experience browser disconnect really often e which fails my build pretty much all the time, since karma considers a browser disconnect is an error (see the "DISCONNECT" in https://travis-ci.org/yhwh/stimuli/builds/12038888). So I added a disconnect tolerance option, which allow to rerun the browser tests (a specified amount of time) in case of disconnection and my build went green again (see the "DISCONNECT" in https://travis-ci.org/yhwh/stimuli/builds/12072006).
Outside of my own build scope, I think this option would be very useful when you run tests on a complex app with a flaky connection between the browsers and the server (wifi, cloud etc...).

Also I didn't write any tests for this since I didn't see in the build and in the test folder a normalised way to write integration tests of this kind, I would suggest to use node-webkit to create a custom test processor since it allows to mix the node context with a webkit context. 
For example it would be great to have this for testing communication between the client and the server, if you want me to help for this let me know...