History log of /external/autotest/server/site_tests/bluetooth_Sanity_ValidAddress/bluetooth_Sanity_ValidAddress.py
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
8d2cbf363de4aace06c65ddd20ec862431ce928c 12-Nov-2013 Scott James Remnant <keybuk@chromium.org> Bluetooth: rename BluetoothClient to BluetoothDevice

The BluetoothClient class, and BluetoothClientXmlRpcServer, were named
to match the WiFiClient class that they were based on. However for
Bluetooth tests, the DUT can actually behave as either a Client or a
Server depending on the requirements of the test - with the Tester
likewise behaving as a Server or Client appropriately.

This becomes confusing, so instead rename BluetoothClient to
BluetoothDevice so it's clear it refers to the DUT rather than its role.

BUG=chromium:256771
TEST=test_that suite:bluetooth_sanity

Change-Id: I75864de27325f3a74394a092ce7e538d8161f8a8
Reviewed-on: https://chromium-review.googlesource.com/176468
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Queue: Scott James Remnant <keybuk@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
/external/autotest/server/site_tests/bluetooth_Sanity_ValidAddress/bluetooth_Sanity_ValidAddress.py
1ca2e0e1b6cd0b6f5c2b972e44f3f63539d1dda6 01-Aug-2013 Scott James Remnant <keybuk@chromium.org> Bluetooth: implement first two Sanity checks

Check that the DUT has a Bluetooth adapter, and check that the Bluetooth
adapter address is not garbage.

BUG=chromium:256771
TEST=run_remote_tests

Change-Id: I0b87bf25ea103591c8eab2884e519a32c82f6c72
Reviewed-on: https://gerrit.chromium.org/gerrit/64003
Reviewed-by: Simran Basi <sbasi@chromium.org>
Commit-Queue: Scott James Remnant <keybuk@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
/external/autotest/server/site_tests/bluetooth_Sanity_ValidAddress/bluetooth_Sanity_ValidAddress.py