| edee53af640320049db8368ddbe97fe2500da28c |
|
17-Nov-2015 |
Miao Chou <mcchou@google.com> |
autotest(Bluetooth): Update bluetooth_tester to adopt RpcServerTracker
Update bluetooth_test.py to adopt RpcServerTracker. This solves the failure of
Bluetooth test setup.
BUG=chrome-os-partner:47770
TEST=test_that -b $BOARD chromeos1-row3-rack9-host1.cros
bluetooth_SDP_ServiceSearchRequestBasic
Change-Id: Icb5e6dff28bb4dce896d3abc9b054882889bd0dd
Reviewed-on: https://chromium-review.googlesource.com/313012
Commit-Ready: Miao-chen Chou <mcchou@chromium.org>
Tested-by: Miao-chen Chou <mcchou@chromium.org>
Reviewed-by: Roshan Pius <rpius@chromium.org>
/external/autotest/server/cros/bluetooth/bluetooth_tester.py
|
| e0b08e6170b57f90262726eb7f04e059cb47419c |
|
11-Aug-2015 |
Hsinyu Chao <hychao@chromium.org> |
Revert "autotest: move constants to common_lib"
This reverts commit a4ac7a8f67d61f8a616724f9426dbc0fce71ce69.
BUG=chromium:519353
Change-Id: Iec2873ad22b5bb90e46a9e5b323f9626a2c07d9b
Reviewed-on: https://chromium-review.googlesource.com/292347
Reviewed-by: Hsinyu Chao <hychao@chromium.org>
Commit-Queue: Hsinyu Chao <hychao@chromium.org>
Tested-by: Hsinyu Chao <hychao@chromium.org>
Reviewed-by: Sonny Rao <sonnyrao@chromium.org>
Commit-Queue: Sonny Rao <sonnyrao@chromium.org>
Tested-by: Sonny Rao <sonnyrao@chromium.org>
/external/autotest/server/cros/bluetooth/bluetooth_tester.py
|
| a4ac7a8f67d61f8a616724f9426dbc0fce71ce69 |
|
06-Aug-2015 |
Eric Caruso <ejcaruso@chromium.org> |
autotest: move constants to common_lib
This file gets imported from lots of server-side tests and
infrastructure so it shouldn't be hiding in client/cros. This
moves the file and fixes all imports.
BUG=chromium:485834
TEST=run many tests, make sure there are no problems importing
constants
Change-Id: I5c2b2a0bef6ebc998e62f40162a6ec9cc4436480
Reviewed-on: https://chromium-review.googlesource.com/291302
Trybot-Ready: Eric Caruso <ejcaruso@chromium.org>
Commit-Queue: Eric Caruso <ejcaruso@chromium.org>
Tested-by: Eric Caruso <ejcaruso@chromium.org>
Reviewed-by: Chris Sosa <sosa@google.com>
/external/autotest/server/cros/bluetooth/bluetooth_tester.py
|
| 88aa143caccd16c79016e984cc69a2fbf7547de1 |
|
30-Jul-2015 |
Katherine Threlkeld <kathrelkeld@chromium.org> |
Autotest: grab additional logging in bluetooth autotests
For the Bluetooth tests which run in the wificells, there are two
involved devices: a DUT and a tester. The server side test creates
xmlrpc connections to both devices.
1. Create logging files on each device, to which logging and command
results are piped.
2. Grab the test results. Normally, sysinfo changes are grabbed
automatically. This test setup has two hosts, which the default
logger is not intended to handle. Instead, copy logs explicitly.
Having logs from the DUT and tester, rather than just the server
side test, will ease debugging attempts.
BUG=chromium:426260
TEST=ran all bluetooth tests on a lab wificell: see all logs
Change-Id: I046726957f0fa83e65d29ec3982142af8c9949cb
Reviewed-on: https://chromium-review.googlesource.com/289860
Reviewed-by: Kris Rambish <krisr@chromium.org>
Commit-Queue: Katherine Threlkeld <kathrelkeld@chromium.org>
Tested-by: Katherine Threlkeld <kathrelkeld@chromium.org>
/external/autotest/server/cros/bluetooth/bluetooth_tester.py
|
| 275ecaf0baf905cf69b0c144aac1ae905857cd9c |
|
08-Jan-2015 |
Artem Rakhov <arakhov@chromium.org> |
Bluetooth Autotest: fix data transfer over XMLRPC
We transfer responses returned from Service Search/Attribute requests over
XML RPC. But some values (for example, 128-bit UUIDs) may exceed standard
XML's 64-bit long int. This CL adds json dumps/loads to serialize and
deserialize data, so that we will not have such types mismatch problems in
future.
BUG=chromium:446559
TEST=test_that -b $BOARD $HOST suite:bluetooth_qualification
Change-Id: I57f4207b46c7041d5f6dacbb68095340727636e9
Reviewed-on: https://chromium-review.googlesource.com/239314
Tested-by: Artem Rakhov <arakhov@chromium.org>
Reviewed-by: Scott Remnant <keybuk@chromium.org>
Commit-Queue: Artem Rakhov <arakhov@chromium.org>
/external/autotest/server/cros/bluetooth/bluetooth_tester.py
|
| 6b1d9e7eb7cc38012597d1ce4dcae2a6f39175a3 |
|
14-Dec-2014 |
Christopher Wiley <wiley@chromium.org> |
autotest: Consolidate WiFi/Bluetooth DNS name mangling
Adopt Bluetooth's style of rejecting IP addresses rather than
checking anything that doesn't look like the lab domain names.
Always prefer commandline specified hostnames to inferred hostnames.
While here, remove some WiFi test methods without callsites.
BUG=None
TEST=All of the following pass:
network_WiFi_SimpleConnect.wifi_checkWPA_TKIP (w/wo router_addr)
network_WiFi_AttenuatedPerf.ht40_c001
bluetooth_Sanity_Discovery
Change-Id: Ia76b0e159daeb6fe694dabd56a73fe544371de26
Reviewed-on: https://chromium-review.googlesource.com/236657
Reviewed-by: Christopher Wiley <wiley@chromium.org>
Commit-Queue: Christopher Wiley <wiley@chromium.org>
Tested-by: Christopher Wiley <wiley@chromium.org>
/external/autotest/server/cros/bluetooth/bluetooth_tester.py
|
| e686dcc4914aaf44164ce0cb9bd5dd243477fa76 |
|
06-Dec-2014 |
Scott James Remnant <keybuk@chromium.org> |
bluetooth: test LE Discovery
BUG=chromium:439654
TEST=test_that $IP bluetooth_Sanity_LEDiscovery
Change-Id: I677fa9e3cd9bd12b5bde280152549db9adcb8ec8
Reviewed-on: https://chromium-review.googlesource.com/233721
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Commit-Queue: Scott James Remnant <keybuk@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
/external/autotest/server/cros/bluetooth/bluetooth_tester.py
|
| 2562204037547fb7d2a012b70dcffbc12585731c |
|
05-Dec-2014 |
Scott James Remnant <keybuk@chromium.org> |
Bluetooth: allow tester IP to be specified in --args
Normally the tester hostname is derived from the DUT hostname by
appending '-router' to the first part. This requires manual /etc/hosts
entries on your workstation when dealing with machines by IP address.
Allowing the IP (or hostname) of the tester to be specified on the
command-line with '--args tester=IP' makes this much easier to handle.
BUG=none
TEST=test_that $DUT_IP bluetooth_Sanity_Discovery --args tester=$TESTER_IP
Change-Id: Ic113cb73a2de95e60b75931d95f2b1ea7ba4a2cf
Reviewed-on: https://chromium-review.googlesource.com/233492
Reviewed-by: Michael Janssen <jamuraa@chromium.org>
Commit-Queue: Scott James Remnant <keybuk@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
/external/autotest/server/cros/bluetooth/bluetooth_tester.py
|
| ef5a458439a763afa1937837cdf5b6d7065be74d |
|
30-Oct-2014 |
Artem Rakhov <arakhov@chromium.org> |
Bluetooth SDP autotest: ServiceSearchAttribute invalid requests
This CL adds 2 tests to check invalid Service Search Attribute requests.
One test sends a request with intentionally invalid syntax, the other one
sends requests with wrong PDU size.
BUG=chromium:417931
TEST=test_that --board ${BOARD} ${HOSTNAME} bluetooth_SDP_ServiceSearchAttributeRequest
Change-Id: If38e2d48381f08022eeaa8cfb54c96d8c1206795
Reviewed-on: https://chromium-review.googlesource.com/226381
Tested-by: Artem Rakhov <arakhov@chromium.org>
Reviewed-by: Michael Janssen <jamuraa@chromium.org>
Reviewed-by: Arman Uguray <armansito@chromium.org>
Commit-Queue: Artem Rakhov <arakhov@chromium.org>
/external/autotest/server/cros/bluetooth/bluetooth_tester.py
|
| f53eeec1740214b1838f577559ba0acd856e996c |
|
25-Sep-2014 |
Artem Rakhov <arakhov@chromium.org> |
Bluetooth SDP autotest: Bluetooth Tester to support Service Search Attribute
This CL adds Service Search Attribute Request method to BluetoothTester and
BluetoothTesterXmlRpcDelegate classes.
BUG=chromium:416168
TEST=pylint; use methods on stumpy and peppy
Change-Id: Idb8adfe35424c9697fab5ed9dd72c704da56f272
Reviewed-on: https://chromium-review.googlesource.com/219886
Tested-by: Artem Rakhov <arakhov@chromium.org>
Reviewed-by: Michael Janssen <jamuraa@chromium.org>
Reviewed-by: Arman Uguray <armansito@chromium.org>
Commit-Queue: Artem Rakhov <arakhov@chromium.org>
/external/autotest/server/cros/bluetooth/bluetooth_tester.py
|
| af4e4a6932ecbb6744e48f4f9e2dcc12f3ba9d50 |
|
12-Jun-2014 |
Artem Rakhov <arakhov@chromium.org> |
Bluetooth SDP autotest: tests for invalid Service Attribute Requests
This CL adds tests for invalid Service Attribute Requests:
TP/SERVER/SA/BI-01-C - invalid record handle
TP/SERVER/SA/BI-02-C - invalid syntax of request
TP/SERVER/SA/BI-03-C - invalid size of request in header
It also adds corresponding parameters to service_attribute_request()
method of bluetooth_sdp_socket() to be able to send intentionally
invalid requests.
BUG=chromium:329044
TEST=test_that --board ${BOARD} ${HOSTNAME} bluetooth_SDP_ServiceAttributeRequest
Change-Id: Idd8d7fcc5ff807af03d4d5f50a8927501f402ac9
Reviewed-on: https://chromium-review.googlesource.com/203560
Tested-by: Artem Rakhov <arakhov@chromium.org>
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Reviewed-by: Prashanth B <beeps@chromium.org>
Reviewed-by: Arman Uguray <armansito@chromium.org>
Commit-Queue: Artem Rakhov <arakhov@chromium.org>
/external/autotest/server/cros/bluetooth/bluetooth_tester.py
|
| ebf3df32a3bfa32782ffdc8e0ce5bf6d65734d5d |
|
01-Apr-2014 |
Artem Rakhov <arakhov@chromium.org> |
Bluetooth SDP autotest: basic Service Attribute Request
Service Attribute Request is used to retrieve specified attribute values from
a specific service record. The service record handle of the desired service
record and a list of desired attribute IDs to be retrieved from that service
record are supplied as parameters.
This CL adds Service Attribute Request support to SDP Socket class,
as well as to all classes that are used to expose it's methods for autotest.
The CL also implements the very basic test for this type of request,
which is 'TP/SERVER/SA/BV-01-C' from SDP test specification.
BUG=chromium:329044
TEST=test_that --board ${BOARD} ${HOSTNAME} bluetooth_SDP_ServiceAttributeRequest
Change-Id: I4b236a331fea661584c396a2c3ff937bf91c2102
Reviewed-on: https://chromium-review.googlesource.com/196404
Tested-by: Artem Rakhov <arakhov@chromium.org>
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Commit-Queue: Artem Rakhov <arakhov@chromium.org>
/external/autotest/server/cros/bluetooth/bluetooth_tester.py
|
| f42dc83292497e95cf4f41c6463f697b840826e2 |
|
03-Mar-2014 |
Artem Rakhov <arakhov@chromium.org> |
Bluetooth SDP autotest: Service Search Request with invalid syntax
This CL adds the last test for SDP Service Search Request, which checks if
response for request with invalid syntax is correct. It is implementation of
test case 'TP/SERVER/SS/BI-02-C' from SIG Bluetooth Test Specification.
However, the specification itself doesn't specify the format of invalid request
(it's not clear, what exactly should be invalid). So testers are free to send
any invalid request. This implementation sends requests without continuation
state parameter, so that the requests are invalid, but still are very close to
valid format. The latest BlueZ unit-tests also do the same invalid requests.
BUG=chromium:329044
TEST=test_that --board ${BOARD} ${HOSTNAME} bluetooth_SDP_ServiceSearchRequestBasic
Change-Id: I4fbd9eae20d440d75849286cdd80ac157e4bb1bb
Reviewed-on: https://chromium-review.googlesource.com/189243
Tested-by: Artem Rakhov <arakhov@chromium.org>
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Commit-Queue: Artem Rakhov <arakhov@chromium.org>
/external/autotest/server/cros/bluetooth/bluetooth_tester.py
|
| ba130384b49108dcfa91ad7751b825c0d0128963 |
|
27-Feb-2014 |
Artem Rakhov <arakhov@chromium.org> |
Bluetooth SDP autotest: Service Search Request with invalid PDU size
Added new SDP autotest, which implements test case 'TP/SERVER/SS/BI-01-C' from
Bluetooth SIG Test Spec. It verifies that the IUT behaves correctly when it
receives a request with invalid PDU size. The correct behaviour is to respond
with SDP_ErrorResponse PDU, with the error code 0x0004 (Invalid PDU Size).
In order to support invalid PDU size, forced_pdu_size parameter was added to all
the service_search_request() methods (equals None by default, which means
"calculate from resulting sequence's size").
This CL also adds handling of error responses to BluetoothSDPSocket class: so
service_search_request() method should return error code (as int) in case of
error, and list of found services' records otherwise.
BUG=chromium:329044
TEST=test_that --board ${BOARD} ${HOSTNAME} bluetooth_SDP_ServiceSearchRequestBasic
Change-Id: I93c072b8986498b1464d336fd51f47312d359f09
Reviewed-on: https://chromium-review.googlesource.com/188118
Tested-by: Artem Rakhov <arakhov@chromium.org>
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Commit-Queue: Artem Rakhov <arakhov@chromium.org>
/external/autotest/server/cros/bluetooth/bluetooth_tester.py
|
| 85593071fa1ba66349f9ee61f29393a1581113f6 |
|
26-Feb-2014 |
Scott James Remnant <keybuk@chromium.org> |
Bluetooth: enable suites for nightly runs
Fix the SDP test to use the right suite declaration, add wificell to all
dependencies, and use the -router hostname style to match the wificell
setup.
BUG=chromium:346989
TEST=verify suites are running
Change-Id: I8cbd06d46b15e8fb8d47325b4e0f80911f65123b
Reviewed-on: https://chromium-review.googlesource.com/187953
Reviewed-by: Alex Miller <milleral@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
Commit-Queue: Scott James Remnant <keybuk@chromium.org>
/external/autotest/server/cros/bluetooth/bluetooth_tester.py
|
| ca443b518bfe8457c73d9a0cddadf8f6972a4c64 |
|
11-Jan-2014 |
Artem Rakhov <arakhov@chromium.org> |
Bluetooth SDP autotest: support for 16, 32, 128 UUIDs
Bluetooth Test Specification document says that the tests shall be performed
using 128 bits UUID, 32 bits UUID and 16 bits UUID. So this CL adds an optional
parameter called preferred_size for Service Search Request method. For every
single UUID, if it fits into preferred_size bits, then this size will be used
for request. Otherwise the UUID will be casted to 128 bits format.
BUG=chromium:329044
TEST=use the following command to run it:
test_that --board ${BOARD} ${HOSTNAME} bluetooth_SDP_ServiceSearchRequestBasic
Probably, 'failed_attempts' variable will always be 0
Change-Id: I3dfb3539578182f933c4c650e564c03a97cd8916
Reviewed-on: https://chromium-review.googlesource.com/182251
Tested-by: Artem Rakhov <arakhov@chromium.org>
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Commit-Queue: Artem Rakhov <arakhov@chromium.org>
/external/autotest/server/cros/bluetooth/bluetooth_tester.py
|
| 448d52cd25de24ffd96a882a4445fc7c8326e413 |
|
04-Dec-2013 |
Artem Rakhov <arakhov@google.com> |
BluetoothTester: add support for basic SDP methods
BluetoothTester and BluetoothTesterXmlRpcDelegate classes are used to
expose tester-side bluetooth functionality (BluetoothSocket) so that it
could be accessed in autotests. BluetoothTester runs on the server and
basically represents the tester as an object for autotests.
BluetoothTesterXmlRpcDelegate runs on the tester and is generally a
proxy for BluetoothTester.
This CL adds connect() and service_search_request() methods to these
classes.
BUG=none
TEST=use added methods in autotests
Change-Id: I28671d2ad76d7a3e95f299c9622a6856a41ed941
Reviewed-on: https://chromium-review.googlesource.com/179167
Tested-by: Artem Rakhov <arakhov@chromium.org>
Reviewed-by: Fang Deng <fdeng@chromium.org>
Commit-Queue: Artem Rakhov <arakhov@chromium.org>
/external/autotest/server/cros/bluetooth/bluetooth_tester.py
|
| 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/cros/bluetooth/bluetooth_tester.py
|
| aec4edd340e914885cb1fe26e9b8766788009f2f |
|
27-Aug-2013 |
Scott James Remnant <keybuk@chromium.org> |
Bluetooth: implement bluetooth_Sanity_Discovery
This test is another example of a Bluetooth test with a separate
tester device (stumpy with testbed-ap profile), and is the mirror of
bluetooth_Sanity_Discoverable.
BUG=chromium:256771
TEST=run_remote_tests
Change-Id: I00142fc5183af8466638ef7b1bc64cae4a6c87fb
Reviewed-on: https://chromium-review.googlesource.com/67010
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Commit-Queue: Scott James Remnant <keybuk@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
/external/autotest/server/cros/bluetooth/bluetooth_tester.py
|
| da9f43cc5c84691d82b1dd9222fea37234cb9a0a |
|
08-Aug-2013 |
Scott James Remnant <keybuk@chromium.org> |
Bluetooth: implement bluetooth_Sanity_Discoverable
This test is the first example of a Bluetooth test with a separate
tester device (a stumpy with the testbed-ap profile is the intent).
It can be run two ways:
1. as bluetooth_Sanity_Discoverable - in which case the Tester will
be used to perform a device discovery and verify that the DUT
was detected in the process.
2. as bluetooth_Sanity_Discoverable.manual - in which case only the
DUT is used, and instructions presented on screen for use with
a third-party Tester (such as the Bluetooth PTS).
BUG=chromium:256771
TEST=run_remote_tests
Change-Id: I851a05acff3ca3edba32bb2f0cd043d8042d162d
Reviewed-on: https://gerrit.chromium.org/gerrit/65074
Commit-Queue: Scott James Remnant <keybuk@chromium.org>
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
/external/autotest/server/cros/bluetooth/bluetooth_tester.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/cros/bluetooth/bluetooth_tester.py
|
| 1c72d7adf4148029baa8846eebe9f7e1a287e10f |
|
30-Jul-2013 |
Scott James Remnant <keybuk@chromium.org> |
Add infrastructure for Interactive tests
Inspired by the SemiAuto tests used by the test team, this uses a
similar approach but wrapped in an XML-RPC server deployed to the
client.
BUG=chromium:256771
TEST=server test that uses interactive_client
Change-Id: I8420a2a2ed6fc031b97044d6bbcf32e50cbcf4a4
Reviewed-on: https://gerrit.chromium.org/gerrit/63640
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/cros/bluetooth/bluetooth_tester.py
|
| 4dcd73f7d38d89063911c74796db9aa68ff8b064 |
|
23-Jul-2013 |
Scott James Remnant <keybuk@chromium.org> |
Bluetooth: begin testing infrastructure
Implement an XML-RPC server for both the Client (DUT) and Tester
based off the existing WiFi testing approach, with a server class
to proxy for them.
BUG=chromium:256771
TEST=simple test that instantiates both,
verify xml-rpc server was running on both devices
Change-Id: Icbaf9409460f0d535c160f6a11f1db86f989f46a
Reviewed-on: https://gerrit.chromium.org/gerrit/62890
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
Commit-Queue: Scott James Remnant <keybuk@chromium.org>
/external/autotest/server/cros/bluetooth/bluetooth_tester.py
|