History log of /external/autotest/client/cros/cellular/mbim_compliance/sequences/connect_sequence.py
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
32694e182daed32e30dbc9d13d8af0154660cf1c 13-Jan-2015 Roshan Pius <rpius@chromium.org> mbim_compliance: Data transfer tests bug fixes.

1. Fixed the signature of the NDP header to use decimal connection ID
instead of the ASCII connection ID.
2. NTB32 format setting may not be supported by all devices, so add
appropriate error message and bail out of those tests.
3. Couple of bug fixes uncovered in the tests.
4. Integrated MBIM assertions to optimally use the autotest assertion
framework.

BUG=chromium:440552
TEST='test_that ${host} e:cellular_MbimComplianceDataTransfer.DTS.*'

Change-Id: I7933d878ecb3b22c32fff32c2728fc19a528fccf
Reviewed-on: https://chromium-review.googlesource.com/240549
Reviewed-by: Roshan Pius <rpius@chromium.org>
Commit-Queue: Roshan Pius <rpius@chromium.org>
Tested-by: Roshan Pius <rpius@chromium.org>
/external/autotest/client/cros/cellular/mbim_compliance/sequences/connect_sequence.py
20ea63d02216bbbf3e4d8776f37896113a26a429 10-Dec-2014 Roshan Pius <rpius@chromium.org> mbim_compliance: Add test ERR_01,02,03,04,05 specified in the compliance suite.

These tests validate the error handling of the device for wrongly
formatted command messages.
Modifying the connect sequence to optionally introduce errors.

BUG=chromium:432621
TEST=test_that -b ${board} ${host} suite:network_mbim_compliance

Change-Id: I0c6a384892bb1d3a04a5b53ed647535b044b22cc
Reviewed-on: https://chromium-review.googlesource.com/233913
Reviewed-by: Ben Chan <benchan@chromium.org>
Commit-Queue: Roshan Pius <rpius@chromium.org>
Tested-by: Roshan Pius <rpius@chromium.org>
/external/autotest/client/cros/cellular/mbim_compliance/sequences/connect_sequence.py
b3c9e7a6dad23d6c10fcff9396b9b875285da162 04-Dec-2014 Roshan Pius <rpius@chromium.org> mbim_compliance: Add test CM_15 specified in the compliance suite.

1. Test checks whether the device correctly fragments the control
response
messages when the host sets the max_control_transfer parameter to a
low value in the open sequence.
2. Adding an optional parameter to open sequence invocation to set the
max_control_transfer_size parameter. If not explicitly set by the test,
it defaults to the wMaxControlMessage parameter specified by the device
in the functional descriptor as before.
3. Modifying all existing tests, sequences to use the configure
max_control_transfer size setting for all control transfer operations
rather than assuming it to be set to wMaxControlMessage value specified
in the device functional descriptor.

BUG=chromium:432621
TEST=test_that -b ${board} ${host} suite:network_mbim_compliance

Change-Id: Ic32e551f3dd02f34ad05a2b199405b3a41a6a1b7
Reviewed-on: https://chromium-review.googlesource.com/233231
Reviewed-by: Roshan Pius <rpius@chromium.org>
Commit-Queue: Roshan Pius <rpius@chromium.org>
Tested-by: Roshan Pius <rpius@chromium.org>
/external/autotest/client/cros/cellular/mbim_compliance/sequences/connect_sequence.py
08de03278ead5322675abf7f695a8d22e26e1745 02-Dec-2014 Roshan Pius <rpius@chromium.org> mbim_compliance: Add test CM_14 specified in the compliance suite.

Test checks whether the device responds back with the correct error
message when connect sequence is issued after close sequence.
Adding an optional parameter to sequence invocation to help in
reusing/invoking parts of the sequences.

BUG=chromium:432621
TEST=test_that -b ${board} ${host} suite:network_mbim_compliance

Change-Id: I7d803ac07fa40501929edc8363b8304b6b7b55ab
Reviewed-on: https://chromium-review.googlesource.com/232119
Reviewed-by: Roshan Pius <rpius@chromium.org>
Commit-Queue: Roshan Pius <rpius@chromium.org>
Tested-by: Roshan Pius <rpius@chromium.org>
/external/autotest/client/cros/cellular/mbim_compliance/sequences/connect_sequence.py
e938ff00845c29f56935f2b973dd677793b8d834 25-Nov-2014 Roshan Pius <rpius@chromium.org> mbim_compliance: New MBIM message handling framework.

All MBIM request/response messages now have hierarchial tree like
structure to ease addition of any new message handling. Starting with the
base class MBIMControlMessage, each message class definition becomes the
parent of any subsequent payload message class definitions. This avoids
redundant definitions and helps to propagate the field & default values.

For response message, the _DEFAULTS along with the PAYLOAD_ID field type is
used to identify the received message class.
For request message, the _DEFAULTS will be used to fill up any base
class field values which are fixed for a message type.

Also supports fragmentation/defragmentation of messages if needed.

BUG=chromium:432621
TEST=test_that -b ${board} ${host} suite:network_mbim_compliance
CQ-DEPEND=CL:232937

Change-Id: I551b621879ef8ff10322fa01d6db26a948ff531b
Reviewed-on: https://chromium-review.googlesource.com/231722
Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org>
Commit-Queue: Roshan Pius <rpius@chromium.org>
Tested-by: Roshan Pius <rpius@chromium.org>
/external/autotest/client/cros/cellular/mbim_compliance/sequences/connect_sequence.py
cc38f7e2548b0b33c48fcf3343e41f3f7e5833f7 19-Nov-2014 Roshan Pius <rpius@chromium.org> mbim_compliance: Migrate MBIM tests to autotest framework

Moving the initial set of tests to the autotest framework

BUG=chromium:432621
TEST=test_that -b ${board} ${host} suite:network_mbim_compliance

Change-Id: I7398b9ceb9a1e14f0e9a1c42b7b06d77d97fe3fa
Reviewed-on: https://chromium-review.googlesource.com/229876
Tested-by: Roshan Pius <rpius@chromium.org>
Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org>
Tested-by: Prathmesh Prabhu <pprabhu@chromium.org>
Commit-Queue: Roshan Pius <rpius@chromium.org>
/external/autotest/client/cros/cellular/mbim_compliance/sequences/connect_sequence.py
4d427943bf1931aab7f9992b9f034334e36ec7db 26-Jul-2014 Miao-chen Chou <mcchou@chromium.org> MBIM Compliance: Implement MBIM Data Module, MBIM constants module, Connect Sequence and CM_xx tests.

This CL implements the following features.
- Implement MBIM data module defining information structures encapsulated in the
information buffer field of MBIM command message.
- Implement the unittest of the MBIM data module.
- Implement mbim_constants module.
- Implement connect sequence.
- implement CM_07 test.
- implement CM_08 test.
- implement CM_09 test.
- implement CM_13 test.
- Revise MBIM control message module.

BUG=chromium:393005
TEST=Run CM07Test, CM08Test, CM09Test, CM13Test and mbim_data_unittest.py.

Change-Id: If825d91757dd8ee975fdb83ffa46bc74e30da8fd
Reviewed-on: https://chromium-review.googlesource.com/210591
Reviewed-by: Ben Chan <benchan@chromium.org>
Tested-by: Ben Chan <benchan@chromium.org>
Commit-Queue: Ben Chan <benchan@chromium.org>
/external/autotest/client/cros/cellular/mbim_compliance/sequences/connect_sequence.py