bluetooth: Refactor how we update based on Advertising Data

chrome/test/data/extensions/api_test/bluetooth/device_info/runtest.js

Index: chrome/test/data/extensions/api_test/bluetooth/device_info/runtest.js
diff --git a/chrome/test/data/extensions/api_test/bluetooth/device_info/runtest.js b/chrome/test/data/extensions/api_test/bluetooth/device_info/runtest.js
index be22e1628b7b03f23549c24db5a4e186d5501b19..c32becf024f0a75c2c938eb4fa577adc12e32467 100644
--- a/chrome/test/data/extensions/api_test/bluetooth/device_info/runtest.js
+++ b/chrome/test/data/extensions/api_test/bluetooth/device_info/runtest.js
@@ -14,10 +14,10 @@ function testDeviceInfo() {
   chrome.test.assertEq('computer', devices[0].type);
 
   chrome.test.assertEq(2, devices[0].uuids.length);
-  chrome.test.assertEq('00001105-0000-1000-8000-00805f9b34fb',
-                       devices[0].uuids[0]);
-  chrome.test.assertEq('00001106-0000-1000-8000-00805f9b34fb',
-                       devices[0].uuids[1]);
+
+  let uuids = new Set(devices[0].uuids);

[Jeffrey Yasskin, 2016/08/18 16:04:32]

We should alert the extensions/apps team that the order of UUIDs is changing,
which might break some apps. (Even though the behavior is allowed by
https://developer.chrome.com/apps/bluetooth#property-Device-uuids)

[ortuno, 2016/08/19 20:50:32]

I'll add rkc as a reviewer of extensions code.

+  chrome.test.assertTrue(uuids.has('00001105-0000-1000-8000-00805f9b34fb'));
+  chrome.test.assertTrue(uuids.has('00001106-0000-1000-8000-00805f9b34fb'));
 
   chrome.test.assertEq('d2', devices[1].name);
   chrome.test.assertEq(0, devices[1].deviceClass);