Fix foreverFrame test to account for failures prior to timeout

SignalR · Oct 30, 2014 · 2f66221 · 2f66221
1 parent 88d5a95
commit 2f66221
Showing 1 changed file with 6 additions and 4 deletions.
diff --git a/...t.SignalR.Client.JS.Tests/Tests/FunctionalTests/Transports/ForeverFrame/FFConnectFacts.js b/...t.SignalR.Client.JS.Tests/Tests/FunctionalTests/Transports/ForeverFrame/FFConnectFacts.js
@@ -61,10 +61,12 @@ QUnit.asyncTimeoutTest("foreverFrame transport does not trigger verifyLastActive
         end();
     };
 
-    connection._.onFailedTimeoutHandle = window.setTimeout(function () {
-        assert.comment("FailedTimeoutHandle is called.");
-        end();
-    }, 5000);
+    connection.disconnected(function () {
+        assert.comment("Connection successfully transitioned to the disconnecting state.");
+
+        // Give time for any unexpected calls to verifyLastActive
+        window.setTimeout(end, 1000)
+    });
 
     connection.start({ transport: "foreverFrame" }).done(function () {
         assert.fail("Connection should not be connected.");