diff options
author | phajdan.jr@chromium.org <phajdan.jr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-07-14 21:10:49 +0000 |
---|---|---|
committer | phajdan.jr@chromium.org <phajdan.jr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-07-14 21:10:49 +0000 |
commit | ec28f8e18f1ae9593b07a055aa05fd2920fcb044 (patch) | |
tree | f620c691ac68480f98277f1229675719e4b8adee /chrome/browser/browser_browsertest.cc | |
parent | fea93f3d409d1467b794955d156e130e984c2704 (diff) | |
download | chromium_src-ec28f8e18f1ae9593b07a055aa05fd2920fcb044.zip chromium_src-ec28f8e18f1ae9593b07a055aa05fd2920fcb044.tar.gz chromium_src-ec28f8e18f1ae9593b07a055aa05fd2920fcb044.tar.bz2 |
Make BrowserTest.ThirtyFourTabs not-flaky
I converted it to browser_tests framework, so I can just query RenderProcessHost instead of counting "chrome" processes, which apparently induced the flakiness.
TEST=Covered by browser_tests.
http://crbug.com/16062
Review URL: http://codereview.chromium.org/149559
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@20661 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/browser_browsertest.cc')
-rw-r--r-- | chrome/browser/browser_browsertest.cc | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/chrome/browser/browser_browsertest.cc b/chrome/browser/browser_browsertest.cc index f209837..21750e1 100644 --- a/chrome/browser/browser_browsertest.cc +++ b/chrome/browser/browser_browsertest.cc @@ -5,6 +5,7 @@ #include <string> #include "app/l10n_util.h" +#include "base/sys_info.h" #include "chrome/browser/app_modal_dialog.h" #include "chrome/browser/browser.h" #include "chrome/browser/browser_process.h" @@ -98,3 +99,26 @@ IN_PROC_BROWSER_TEST_F(BrowserTest, JavascriptAlertActivatesTab) { EXPECT_EQ(2, browser()->tab_count()); EXPECT_EQ(1, browser()->selected_index()); } + +// Create 34 tabs and verify that a lot of processes have been created. The +// exact number of processes depends on the amount of memory. Previously we +// had a hard limit of 31 processes and this test is mainly directed at +// verifying that we don't crash when we pass this limit. +IN_PROC_BROWSER_TEST_F(BrowserTest, ThirtyFourTabs) { + GURL url(ui_test_utils::GetTestUrl(L".", L"title2.html")); + + // There is one initial tab. + for (int ix = 0; ix != 33; ++ix) { + browser()->AddTabWithURL(url, GURL(), PageTransition::TYPED, + true, 0, false, NULL); + } + EXPECT_EQ(34, browser()->tab_count()); + + // See browser\renderer_host\render_process_host.cc for the algorithm to + // decide how many processes to create. + if (base::SysInfo::AmountOfPhysicalMemoryMB() >= 2048) { + EXPECT_GE(RenderProcessHost::size(), 24U); + } else { + EXPECT_LE(RenderProcessHost::size(), 23U); + } +} |