[remoting-test] Fix It2Me browser test failures.

[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
Committed: https://crrev.com/1a0e0b3bd05234d15f43da0a5b4f1813755e233b
Cr-Commit-Position: refs/heads/master@{#334980}

[kelvinp, 2015-06-18 00:59:54]

kelvinp@chromium.org changed reviewers:
+ jamiewalch@chromium.org

[kelvinp, 2015-06-18 01:00:58]

kelvinp@chromium.org changed reviewers:
+ anandc@chromium.org

[kelvinp, 2015-06-18 01:01:07]

PTAL

[Jamie, 2015-06-18 01:05:30]

lgtm

https://codereview.chromium.org/1178313004/diff/1/remoting/webapp/browser_tes...
File remoting/webapp/browser_test/browser_test.js (right):

https://codereview.chromium.org/1178313004/diff/1/remoting/webapp/browser_tes...
remoting/webapp/browser_test/browser_test.js:288: var onFailure =
browserTest.onUIMode(failureMode, SESSION_CONNECTION_TIMEOUT);
You've also made the test stricter, which is a good thing but should be called
out in the CL description.

[kelvinp, 2015-06-18 01:10:48]

The CQ bit was checked by kelvinp@chromium.org

[commit-bot: I haz the power, 2015-06-18 01:11:29]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1178313004/1

[commit-bot: I haz the power, 2015-06-18 01:44:00]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-06-18 01:45:05]

Patchset 1 (id:??) landed as
https://crrev.com/1a0e0b3bd05234d15f43da0a5b4f1813755e233b
Cr-Commit-Position: refs/heads/master@{#334980}