Sync FileSystem: Add simulated relaunch of DriveFileSyncService on its unit_tests

chrome/browser/sync_file_system/fake_remote_change_processor.cc

 // Copyright (c) 2013 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "chrome/browser/sync_file_system/fake_remote_change_processor.h"
 
 #include "base/bind.h"
 #include "base/files/file_path.h"
 #include "base/location.h"
 #include "base/message_loop_proxy.h"
 #include "webkit/fileapi/file_system_url.h"
 #include "webkit/fileapi/syncable/file_change.h"
 #include "webkit/fileapi/syncable/sync_file_metadata.h"
 
 namespace sync_file_system {
 
 FakeRemoteChangeProcessor::FakeRemoteChangeProcessor() {
 }
 
 FakeRemoteChangeProcessor::~FakeRemoteChangeProcessor() {
 }
 
 void FakeRemoteChangeProcessor::PrepareForProcessRemoteChange(
     const fileapi::FileSystemURL& url,
     const std::string& service_name,
     const PrepareChangeCallback& callback) {
+  SyncFileMetadata local_metadata;
+
+  URLToFileChangesMap::iterator found = applied_changes_.find(url);
+  if (found != applied_changes_.end()) {
+    DCHECK(!found->second.empty());
+    const FileChange& applied_change = found->second.back();
+    if (applied_change.IsAddOrUpdate()) {
+      local_metadata = SyncFileMetadata(
+          applied_change.file_type(),
+          100 /* size */,
+          base::Time::Now());
+    }
+  }

[kinuko, 2013/02/28 13:58:30]

It's ok for this change, but maybe we should rather maintain a map or something
to simulate the local fs image (i.e. maintain the in-memory map based on the
changes applied by ApplyRemoteChange)? That'll make it easier for further
changes.

[tzik, 2013/02/28 14:00:38]

OK, I'll do it next patch.

   base::MessageLoopProxy::current()->PostTask(
       FROM_HERE,
       base::Bind(callback, SYNC_STATUS_OK,
-                 SyncFileMetadata(), FileChangeList()));
+                 local_metadata, FileChangeList()));
 }
 
 void FakeRemoteChangeProcessor::ApplyRemoteChange(
     const FileChange& change,
     const base::FilePath& local_path,
     const fileapi::FileSystemURL& url,
     const SyncStatusCallback& callback) {
   applied_changes_[url].push_back(change);
   base::MessageLoopProxy::current()->PostTask(
       FROM_HERE, base::Bind(callback, SYNC_STATUS_OK));
@@ skipping 12 matching lines @@
   base::MessageLoopProxy::current()->PostTask(
       FROM_HERE, base::Bind(callback, SYNC_STATUS_OK));
 }
 
 const FakeRemoteChangeProcessor::URLToFileChangesMap&
 FakeRemoteChangeProcessor::GetAppliedRemoteChanges() const {
   return applied_changes_;
 }
 
 }  // namespace sync_file_system