Basic implementation of the Sync C++ fake server

chrome/browser/sync/test/integration/prototype_fake_server_test.cc

Index: chrome/browser/sync/test/integration/prototype_fake_server_test.cc
diff --git a/chrome/browser/sync/test/integration/prototype_fake_server_test.cc b/chrome/browser/sync/test/integration/prototype_fake_server_test.cc
new file mode 100644
index 0000000000000000000000000000000000000000..50cbabe7e3f7a1c237c8ea28f58e2023d0523820
--- /dev/null
+++ b/chrome/browser/sync/test/integration/prototype_fake_server_test.cc
@@ -0,0 +1,24 @@
+// 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/test/integration/sync_test.h"
+
+class PrototypeFakeServerTest : public SyncTest {
+ public:
+  PrototypeFakeServerTest() : SyncTest(SINGLE_CLIENT) {
+    UseFakeServer();
+  }
+
+  virtual ~PrototypeFakeServerTest() {}
+
+ private:
+  DISALLOW_COPY_AND_ASSIGN(PrototypeFakeServerTest);
+};
+
+// TODO(pvalenzuela): Remove this test when sync_integration_tests is

[rlarocque, 2013/12/18 20:22:01]

You should reference the crbug for the fake server development in this comment.

[pval...(no longer on Chromium), 2013/12/19 01:16:56]

Done.

+// transitioned to use the C++ fake server. This test currently exists to
+// ensure fake server functionality during development.
+IN_PROC_BROWSER_TEST_F(PrototypeFakeServerTest, Setup) {
+  ASSERT_TRUE(SetupSync()) << "SetupSync() failed.";

[Raghu Simha, 2013/12/18 22:37:12]

Considering that this test is primarily meant to test the fake server as opposed
to the sync engine, perhaps you could verify that the server is running before
calling SetupSync? And after sync is set up, I wonder if it makes sense to
verify that the server contains the same data as the client. Feel free to do
this now or in a future CL.

[pval...(no longer on Chromium), 2013/12/19 01:16:56]

I like this idea, but would prefer to do it in a future CL. 

+}