New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 607394 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 607395
Owner:
Closed: Apr 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 2
Type: Bug
M52



Sign in to add a comment

Write comprehensive tests for Bluetooth GATT server events.

Project Member Reported by r...@chromium.org, Apr 28 2016

Issue description

Currently 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 great amount 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.
 

Comment 1 by rob@robwu.nl, Apr 28 2016

Mergedinto: 607395
Status: Duplicate (was: Assigned)
Drive-by triage - this looks identical to issue 607395.

Sign in to add a comment