diff options
author | phajdan.jr@chromium.org <phajdan.jr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-02-15 07:35:37 +0000 |
---|---|---|
committer | phajdan.jr@chromium.org <phajdan.jr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-02-15 07:35:37 +0000 |
commit | 79457797443d45463b92abcda0124706bdf1aff5 (patch) | |
tree | 83c22707ecc9649686be8d5bb5bd74913c4520d8 /chrome/chrome_tests.gypi | |
parent | af980796c6c9df7bd06210397ffa5dad155ebf66 (diff) | |
download | chromium_src-79457797443d45463b92abcda0124706bdf1aff5.zip chromium_src-79457797443d45463b92abcda0124706bdf1aff5.tar.gz chromium_src-79457797443d45463b92abcda0124706bdf1aff5.tar.bz2 |
GTTF: Use a fresh TestingBrowserProcess for each test, part #1
This is going to be done in multiple steps,
because lots of tests depend on global TestingBrowserProcess.
However, the current solution is very error-prone,
and may lead to state being carried from one test
to another (via NotificationService), resulting in crashes.
In theory the ScopedTestingBrowserProcess could be made
empty for now, but re-initializing g_browser_process inside it
has two benefits:
1) It verifies that changing g_browser_process actually works.
2) It protects at least a subset of tests from carrying state.
BUG=61062
TEST=unit_tests, possibly more
Review URL: http://codereview.chromium.org/6478005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@74926 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/chrome_tests.gypi')
-rw-r--r-- | chrome/chrome_tests.gypi | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/chrome/chrome_tests.gypi b/chrome/chrome_tests.gypi index 61c87eb..f0c67ba 100644 --- a/chrome/chrome_tests.gypi +++ b/chrome/chrome_tests.gypi @@ -158,6 +158,7 @@ 'test/test_url_request_context_getter.h', 'test/testing_browser_process.cc', 'test/testing_browser_process.h', + 'test/testing_browser_process_test.h', 'test/testing_device_token_fetcher.cc', 'test/testing_device_token_fetcher.h', 'test/testing_pref_service.cc', |