Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(549)

Unified Diff: device/bluetooth/bluez/bluetooth_bluez_unittest.cc

Issue 2751223002: bluetooth: Stop support of reconnecting devices not supporting pairing (Closed)
Patch Set: fix an unittest failure Created 3 years, 9 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: device/bluetooth/bluez/bluetooth_bluez_unittest.cc
diff --git a/device/bluetooth/bluez/bluetooth_bluez_unittest.cc b/device/bluetooth/bluez/bluetooth_bluez_unittest.cc
index 5db8d4fb748e3831d8f896ea2b2a2ba43c74bddc..8d1b1e255392efb6717c395e3f86b2f0a7ba424c 100644
--- a/device/bluetooth/bluez/bluetooth_bluez_unittest.cc
+++ b/device/bluetooth/bluez/bluetooth_bluez_unittest.cc
@@ -2820,15 +2820,13 @@ TEST_F(BluetoothBlueZTest, PairTrustedDevice) {
kConnectedTrustedNotPairedDeviceAddress);
ASSERT_TRUE(device != nullptr);
- // On the DBus level the device is trusted but not paired. But the current
- // implementation of |BluetoothDevice::IsPaired()| returns true in this case.
bluez::FakeBluetoothDeviceClient::Properties* properties =
fake_bluetooth_device_client_->GetProperties(
dbus::ObjectPath(bluez::FakeBluetoothDeviceClient::
kConnectedTrustedNotPairedDevicePath));
EXPECT_FALSE(properties->paired.value());
EXPECT_TRUE(properties->trusted.value());
- ASSERT_TRUE(device->IsPaired());
+ ASSERT_FALSE(device->IsPaired());
// The |kConnectedTrustedNotPairedDevicePath| requests a passkey confirmation.
// Obs.: This is the flow when CrOS triggers pairing with a iOS device.

Powered by Google App Engine
This is Rietveld 408576698