bluetooth: Add FakeBluetooth interface

device/bluetooth/test/fake_bluetooth.h

+// Copyright 2017 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.
+#ifndef DEVICE_BLUETOOTH_TEST_FAKE_BLUETOOTH_H_
+#define DEVICE_BLUETOOTH_TEST_FAKE_BLUETOOTH_H_
+
+#include "base/compiler_specific.h"
+#include "device/bluetooth/public/interfaces/test/fake_bluetooth.mojom.h"
+#include "mojo/public/cpp/bindings/binding.h"
+
+namespace bluetooth {
+
+// Implementation of FakeBluetooth in

[scheib, 2017/04/08 00:59:50]

Now that bluetooth/test has a few parts in it, let's explain them with a
README.md

bluetooth test: a test fixture for validating the implementation of
device/bluetooth

mock files: to enable clients to test themselves with mock versions of
device/bluetooth

fake bluetooth: enable clients to test themselves over a mojo interfaces,
implemented by using the mock files.

[ortuno, 2017/04/10 01:47:49]

We already go into a lot of detail about the different parts of the folder in
device/bluetooth/README. Should I move that to device/bluetooth/test/README.md?

[scheib, 2017/04/10 21:52:31]

At this point I think there's enough test specific details that it makes sense
to document it in a test directory README.md and reference it from
device/bluetooth. But, I care more that we describe it in either vs specifically
which one.

[ortuno, 2017/04/12 05:49:06]

Moved all the testing bits to test/README.md

+// src/device/bluetooth/public/interfaces/test/fake_bluetooth.mojom.
+// Implemented on top of the C++ device/bluetooth API.
+class FakeBluetooth : NON_EXPORTED_BASE(public mojom::FakeBluetooth) {
+ public:
+  FakeBluetooth();
+  ~FakeBluetooth() override;
+
+  static void Create(mojom::FakeBluetoothRequest request);
+
+  void SetLEAvailability(bool available,
+                         const SetLEAvailabilityCallback& callback) override;
+};
+
+}  // namespace bluetooth
+
+#endif  // DEVICE_BLUETOOTH_TEST_FAKE_BLUETOOTH_H_