| commit | 1a0e0b3bd05234d15f43da0a5b4f1813755e233b | |
| author | kelvinp <kelvinp@chromium.org> | |
| Thu, 18 Jun 2015 01:43:49 +0000 (17 18:43 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Thu, 18 Jun 2015 01:44:36 +0000 (18 01:44 +0000) | ||
| tree | 5d7a64a1aedb9d14aaa2fdbd947edca1682d9a29 | treesnapshot (tar.gz zip) |
| parent | c46d374132867eceba26a27e346353086436ee03 | commitdiff |
[remoting-test] Fix It2Me browser test failures.
Currently, we wait for 30s for the session to be connected but we
didn't specify any timeout when waiting for session failure.
As a result, the default timeout of 5 seconds is used.
This CL also makes the test stricter by only failing the test when
the current mode matches the expected failure mode.
Those tests are passing before, this suggests that it takes longer
now for an IT2ME connection to fail, which may be related to the
recent signaling change.
BUG=486872
Review URL: https://codereview.chromium.org/1178313004
Cr-Commit-Position: refs/heads/master@{#334980}
Currently, we wait for 30s for the session to be connected but we
didn't specify any timeout when waiting for session failure.
As a result, the default timeout of 5 seconds is used.
This CL also makes the test stricter by only failing the test when
the current mode matches the expected failure mode.
Those tests are passing before, this suggests that it takes longer
now for an IT2ME connection to fail, which may be related to the
recent signaling change.
BUG=486872
Review URL: https://codereview.chromium.org/1178313004
Cr-Commit-Position: refs/heads/master@{#334980}
| remoting/webapp/browser_test/browser_test.js | diffblobblamehistory |