diff options
| author | grt@chromium.org <grt@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-02-02 14:11:01 +0000 |
|---|---|---|
| committer | grt@chromium.org <grt@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-02-02 14:11:01 +0000 |
| commit | 8f73be933d140c780db67f32ba9990956fad9eff (patch) | |
| tree | 9d94376dee9e163b604bd170ad251e215b4bdc2a /chrome_frame/chrome_frame_activex_base.h | |
| parent | cb77c3bd41bb6421a7d2448592e60f86a215062f (diff) | |
| download | chromium_src-8f73be933d140c780db67f32ba9990956fad9eff.zip chromium_src-8f73be933d140c780db67f32ba9990956fad9eff.tar.gz chromium_src-8f73be933d140c780db67f32ba9990956fad9eff.tar.bz2 | |
Make some CF integration tests ever so slightly more deterministic.
Previously, a magic timeout of 4s was used to end certain tests (listed below). This changes them so that they stop when they're done. This makes the test FASTER in release builds (yay!) and WORK in debug builds (omg!). Given the nature of these tests, I won't be surprised if there's a failure on some combination of OS/IE versions. Hopefully these can be fixed without adding 4s delays.
I found that, at least on my machine, explicitly putting a Cache-control: no-cache header on responses helped make the tests more reliable.
The tests are:
*/FullTabNavigationTest.RefreshContents/*
FullTabDownloadTest.TopLevelPostReissueFromChromeFramePage
*/FullTabNavigationTest.RefreshContentsUATest/*
BUG=none
TEST=win_cf trybot runs chrome_frame_tests.exe, so no special testing is needed.
Review URL: https://chromiumcodereview.appspot.com/9316022
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@120211 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome_frame/chrome_frame_activex_base.h')
0 files changed, 0 insertions, 0 deletions