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

chromeos/dbus/fake_cryptohome_client.cc

Index: chromeos/dbus/fake_cryptohome_client.cc
diff --git a/chromeos/dbus/fake_cryptohome_client.cc b/chromeos/dbus/fake_cryptohome_client.cc
index 8d7e841c85714ee05693669398a561b7c049d368..8952c65eebdcf1b4ea6ff68b37c734993228cad5 100644
--- a/chromeos/dbus/fake_cryptohome_client.cc
+++ b/chromeos/dbus/fake_cryptohome_client.cc
@@ -63,6 +63,9 @@ void FakeCryptohomeClient::ResetAsyncCallStatusHandlers() {
 void FakeCryptohomeClient::SetLowDiskSpaceHandler(
     const LowDiskSpaceHandler& handler) {}
 
+void FakeCryptohomeClient::SetDircryptoMigrationProgressHandler(
+    const DircryptoMigrationProgessHandler& handler) {}
+
 void FakeCryptohomeClient::WaitForServiceToBeAvailable(
     const WaitForServiceToBeAvailableCallback& callback) {
   if (service_is_available_) {
@@ -574,6 +577,14 @@ void FakeCryptohomeClient::FlushAndSignBootAttributes(
   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) {