Write comprehensive tests for Bluetooth GATT server events. |
|||||||||||||
Issue descriptionCurrently the Bluetooth Low Energy GATT server events aren't being tested by API tests. To add API tests for these that are really effective, we need to do the following, a.) Integrate the BluetoothLowEnergyApiTestChromeOs tests with BluetoothTestBlueZ. This will allow us to have a lot of control over our environment. b.) Write tests that simulate real events being sent from DBus all the way to the test app. Without this, our tests will miss considerable amount of coverage. All the code that handles actual events being sent from DBus and back isn't going to get exercised. Currently all extension functions are being tested this way (with actual underlying code being called to test the full stack), we need to add more support code to be able to do the same for events.
,
May 3 2016
,
May 17 2016
,
Jul 12 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 5 2016
This is still important, just removing milestone since it doesn't need to land by any particular branch date.
,
Aug 24 2016
,
Aug 24 2016
,
Aug 24 2016
,
Mar 3 2017
,
Mar 3 2017
,
Mar 3 2017
,
Jan 9 2018
,
Jan 17
James now owns connectivity in Chrome OS UI, over to him. |
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by rob@robwu.nl
, Apr 28 2016