Fix unit_tests in notouch mode
Some tests have incorrect expectations given the features
enabled in this mode. The safe browsing tests were failing
due to using the v4 database which required pumping messages
on the IO thread to complete initialization.
Bug: 974405
Change-Id: I238ab3b9d4f87603c3c79a45ab2c2492dee27fa3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1674044
Commit-Queue: Ian Vollick <[email protected]>
Reviewed-by: Mihai Sardarescu <[email protected]>
Reviewed-by: Varun Khaneja <[email protected]>
Reviewed-by: Min Qin <[email protected]>
Reviewed-by: Gabriel Charette <[email protected]>
Cr-Commit-Position: refs/heads/master@{#672544}
diff --git a/chrome/browser/prefs/incognito_mode_prefs_unittest.cc b/chrome/browser/prefs/incognito_mode_prefs_unittest.cc
index 9f75dbc..0fe41ca 100644
--- a/chrome/browser/prefs/incognito_mode_prefs_unittest.cc
+++ b/chrome/browser/prefs/incognito_mode_prefs_unittest.cc
@@ -32,9 +32,9 @@
EXPECT_EQ(IncognitoModePrefs::FORCED, incognito);
EXPECT_FALSE(IncognitoModePrefs::IntToAvailability(10, &incognito));
- EXPECT_EQ(IncognitoModePrefs::ENABLED, incognito);
+ EXPECT_EQ(IncognitoModePrefs::kDefaultAvailability, incognito);
EXPECT_FALSE(IncognitoModePrefs::IntToAvailability(-1, &incognito));
- EXPECT_EQ(IncognitoModePrefs::ENABLED, incognito);
+ EXPECT_EQ(IncognitoModePrefs::kDefaultAvailability, incognito);
}
TEST_F(IncognitoModePrefsTest, GetAvailability) {
