Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(2475)

Unified Diff: chrome/test/in_process_browser_test.h

Issue 1822001: Revert "[Third time landing] Python implementation of sync server, for testing." (Closed)
Patch Set: Created 10 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « chrome/chrome_tests.gypi ('k') | chrome/test/in_process_browser_test.cc » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: chrome/test/in_process_browser_test.h
diff --git a/chrome/test/in_process_browser_test.h b/chrome/test/in_process_browser_test.h
index 63cad3b201301996e17ea6ad1552f29c9829af6c..2b63b7fab8dca5970a0d837ed7d86f266a560204 100644
--- a/chrome/test/in_process_browser_test.h
+++ b/chrome/test/in_process_browser_test.h
@@ -56,6 +56,10 @@ class InProcessBrowserTest : public testing::Test {
// Restores state configured in SetUp.
virtual void TearDown();
+ // This method is used to decide if user data dir
+ // needs to be deleted or not.
+ virtual bool ShouldDeleteProfile() { return true; }
+
protected:
// Returns the browser created by CreateBrowser.
Browser* browser() const { return browser_; }
@@ -63,12 +67,6 @@ class InProcessBrowserTest : public testing::Test {
// Override this rather than TestBody.
virtual void RunTestOnMainThread() = 0;
- // Helper to initialize the user data directory. Called by SetUp() after
- // erasing the user data directory, but before any browser is launched.
- // If a test wishes to set up some initial non-empty state in the user
- // data directory before the browser starts up, it can do so here.
- virtual void SetUpUserDataDirectory() {};
-
// We need these special methods because InProcessBrowserTest::SetUp is the
// bottom of the stack that winds up calling your test method, so it is not
// always an option to do what you want by overriding it and calling the
« no previous file with comments | « chrome/chrome_tests.gypi ('k') | chrome/test/in_process_browser_test.cc » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698