Verify Generic Attribute Profile client behavior when the
Write Characteristic Value procedure fails due to invalid
handle.
---
unit/test-gatt.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/unit/test-gatt.c b/unit/test-gatt.c
index 66b5794..9781b0e 100644
--- a/unit/test-gatt.c
+++ b/unit/test-gatt.c
@@ -787,6 +787,14 @@ static const struct test_step test_write_1 = {
.length = 0x03
};
+static const struct test_step test_write_2 = {
+ .handle = 0x0000,
+ .func = test_write,
+ .expected_att_ecode = 0x01,
+ .value = write_data_1,
+ .length = 0x03
+};
+
static void att_write_cb(struct gatt_db_attribute *att, int err,
void *user_data)
{
@@ -2879,5 +2887,11 @@ int main(int argc, char *argv[])
raw_pdu(0x12, 0x07, 0x00, 0x01, 0x02, 0x03),
raw_pdu(0x13));
+ define_test_client("/TP/GAW/CL/BI-02-C", test_client, service_db_1,
+ &test_write_2,
+ SERVICE_DATA_1_PDUS,
+ raw_pdu(0x12, 0x00, 0x00, 0x01, 0x02, 0x03),
+ raw_pdu(0x01, 0x12, 0x00, 0x00, 0x01));
+
return tester_run();
}
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
