Initial clear server data impl

chrome/browser/sync/test/integration/profile_sync_service_harness.h

Index: chrome/browser/sync/test/integration/profile_sync_service_harness.h
diff --git a/chrome/browser/sync/test/integration/profile_sync_service_harness.h b/chrome/browser/sync/test/integration/profile_sync_service_harness.h
index b4b82eb24c0a4f98daa69dad2a1b7ed36558a8a8..51a02cf66d35e63fb09d3c3b759ddc7339f01fbb 100644
--- a/chrome/browser/sync/test/integration/profile_sync_service_harness.h
+++ b/chrome/browser/sync/test/integration/profile_sync_service_harness.h
@@ -59,6 +59,19 @@ class ProfileSyncServiceHarness {
   // in |synced_datatypes|.
   bool SetupSync(syncer::ModelTypeSet synced_datatypes);
 
+  // Setup sync without the authenticating through the passphrase encryption.
+  // Use this method when you need to setup a client that you're going to cal

[skym, 2017/03/07 18:38:22]

cal should be call

[wylieb, 2017/03/07 19:52:23]

Done.

+  // RestartSyncService() directly after.
+  bool SetupSyncForClear();
+
+  // Same as above, but allows specification of datatypes.
+  bool SetupSyncForClear(syncer::ModelTypeSet synced_datatypes);
+
+  // Restart sync service to simulate a sign-in/sign-out. This is useful
+  // to recover from a lost birthday. Use directly after a clear server data
+  // command to start from clean slate.
+  bool RestartSyncService();
+
   // Calling this acts as a barrier and blocks the caller until |this| and
   // |partner| have both completed a sync cycle.  When calling this method,
   // the |partner| should be the passive responder who responds to the actions
@@ -88,11 +101,17 @@ class ProfileSyncServiceHarness {
   // method for the definition of engine initialization.
   bool AwaitEngineInitialization();
 
+  // Same as above, but without checks for passphrase decryption.

[pavely, 2017/03/07 07:26:16]

Could you explain in CL description/comment why code shouldn't check for
passphrase decryption? Also put some info in description about what problem you
are solving and how you are doing it.

[wylieb, 2017/03/07 19:52:23]

Done.

+  bool AwaitEngineInitializationForClear();
+
   // Blocks the caller until sync setup is complete. Returns true if and only
   // if sync setup completed successfully. See syncer::SyncService's
   // IsSyncActive() method for the definition of what successful means here.
   bool AwaitSyncSetupCompletion();
 
+  // Saem as above, but without checks for passphrase decryption.

[skym, 2017/03/07 18:38:22]

Saem should be Same

[wylieb, 2017/03/07 19:52:23]

Done.

+  bool AwaitSyncSetupCompletionForClear();
+
   // Returns the ProfileSyncService member of the sync client.
   browser_sync::ProfileSyncService* service() const { return service_; }