cryptohome: Add dbus method and signal name for encryption migration.

chromeos/dbus/fake_cryptohome_client.cc

 // Copyright 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 "chromeos/dbus/fake_cryptohome_client.h"
 
 #include <stddef.h>
 #include <stdint.h>
 
 #include "base/bind.h"
@@ skipping 45 matching lines @@
 }
 
 void FakeCryptohomeClient::ResetAsyncCallStatusHandlers() {
   async_call_status_handler_.Reset();
   async_call_status_data_handler_.Reset();
 }
 
 void FakeCryptohomeClient::SetLowDiskSpaceHandler(
     const LowDiskSpaceHandler& handler) {}
 
+void FakeCryptohomeClient::SetDircryptoMigrationProgressHandler(
+    const DircryptoMigrationProgessHandler& handler) {}
+
 void FakeCryptohomeClient::WaitForServiceToBeAvailable(
     const WaitForServiceToBeAvailableCallback& callback) {
   if (service_is_available_) {
     base::ThreadTaskRunnerHandle::Get()->PostTask(FROM_HERE,
                                                   base::Bind(callback, true));
   } else {
     pending_wait_for_service_to_be_available_callbacks_.push_back(callback);
   }
 }
 
@@ skipping 491 matching lines @@
   ReturnProtobufMethodCallback(reply, callback);
 }
 
 void FakeCryptohomeClient::FlushAndSignBootAttributes(
     const cryptohome::FlushAndSignBootAttributesRequest& request,
     const ProtobufMethodCallback& callback) {
   cryptohome::BaseReply reply;
   ReturnProtobufMethodCallback(reply, callback);
 }
 
+void FakeCryptohomeClient::MigrateToDircrypto(
+    const cryptohome::Identification& cryptohome_id,
+    const cryptohome::AuthorizationRequest& auth,
+    const ProtobufMethodCallback& callback) {
+  cryptohome::BaseReply reply;
+  ReturnProtobufMethodCallback(reply, callback);

[Darren Krahn, 2017/03/14 16:03:33]

Make a few progress calls to test the handler?

[kinaba, 2017/03/15 08:17:30]

Good point.

Actually, @fukino is now writing an UI code that drives these
Cryptohome methods, and completing the FakeCryptohomeClient
implementation so that it suits well with the tested UI part.

Is it ok for you to keep this as-is in this CL, and enhance
in a later code that needs to be tested comes in?

+}
+
 void FakeCryptohomeClient::SetServiceIsAvailable(bool is_available) {
   service_is_available_ = is_available;
   if (is_available) {
     std::vector<WaitForServiceToBeAvailableCallback> callbacks;
     callbacks.swap(pending_wait_for_service_to_be_available_callbacks_);
     for (size_t i = 0; i < callbacks.size(); ++i)
       callbacks[i].Run(is_available);
   }
 }
 
@@ skipping 45 matching lines @@
   callback.Run(async_call_id_);
   if (!async_call_status_data_handler_.is_null()) {
     base::ThreadTaskRunnerHandle::Get()->PostTask(
         FROM_HERE, base::Bind(async_call_status_data_handler_, async_call_id_,
                               true, data));
   }
   ++async_call_id_;
 }
 
 }  // namespace chromeos