Using browserDisconnectTolerance invalidates test suite

[kirahowe]

Expected behaviour

When a test fails, karma says that the test failed.

Actual behaviour

When a test fails and chrome disconnects then reconnects (which is allowed if the browserDisconnectTolerance is set to something greater than 0), karma will only report the results of the tests that have run since reconnecting, ignoring any test failures from before chrome disconnected.

Environment Details

• Karma version (output of karma --version): 1.7.1
• Relevant part of your karma.config.js file:

    browserDisconnectTolerance: 1

Steps to reproduce the behaviour

1. Set browserDisconnectTolerance to anything greater than 0.
2. Run a test that fails before the browser disconnects, then after reconnecting run a test that passes
3. Expected: The build should fail and karma should report the test failure from before the disconnection
   Actual: The build passes because karma only reports the results of tests run since the reconnection

[lusarz]

What is the easiest way to reproduce browser disconnection ?

[johnjbarton]

You can try setting the option introduced in #3102 to 1ms. Otherwise I guess you have to create a special test client.html that drops the connection.

[SayWhat69]

Have the same problem here.
Karma doesn't report any tests that were run before the timeout.

[M1ghty1]

Same here.
Doesn't this issue make browserDisconnectTolerance completely useless?