| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the Write
Long Characteristic Value procedure fails due to insufficient
authorization.
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the Write
Long Characteristic Value procedure fails due to write not permitted.
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the Write
Long Characteristic Value procedure fails due to invalid handle.
|
|
|
|
|
| |
Verify that a Generic Attribute Profile client can write a long
Characteristic Value selected by handle.
|
|
|
|
|
| |
This seems to fix problems of make check not working in 32 bit systems
with gcc 5.0.
|
|
|
|
|
| |
Verify that a Generic Attribute Profile server can support cancel
of a reliable write.
|
|
|
|
|
|
|
| |
Verify that a Generic Attribute Profile server can detect and
reject a Characteristic Value Reliable Write Request to a
non-writeable Characteristic Value and issue a Write Not
Permitted Response.
|
|
|
|
|
|
| |
Verify that a Generic Attribute Profile server can detect and
reject a Reliable Write Request to an invalid Characteristic
handle and issue an Invalid Handle Response.
|
|
|
|
|
| |
Verify that a Generic Attribute Profile server can support nested
reliable writing to long Characteristic Values selected by handle.
|
|
|
|
|
| |
Verify that a Generic Attribute Profile server can support reliable
writing to a Characteristic Value selected by handle.
|
|
|
|
|
| |
This verify the code is able to parse services with different gaps
between handles.
|
|
|
|
|
| |
This veryfy we the code is able to parse services with gaps between
handles.
|
|
|
|
|
| |
This is similar to TP/GAD/CL/BV-06-C but using bt_gatt_client to
discover everything.
|
|
|
|
|
|
| |
Verify that a Generic Attribute Profile server can detect and reject
a Write long characteristic descriptor Request to a non-writeable
long characteristic descriptor and issue a Write Not Permitted Response.
|
|
|
|
|
|
| |
Verify that a Generic Attribute Profile server can detect a Write
long characteristic descriptor Request with an invalid characteristic
handle and issue an Invalid Handle Response.
|
|
|
|
|
| |
Verify that a Generic Attribute Profile server can support writing
a long characteristic descriptor selected by handle.
|
|
|
|
|
|
| |
Verify that a Generic Attribute Profile server can detect and reject
a Write Long Characteristic Value Request to a non-writeable long
Characteristic Value and issue a Write Not Permitted Response.
|
|
|
|
|
|
| |
Verify that a Generic Attribute Profile server can detect a Write
Long Characteristic Request with an invalid characteristic handle
and issue an Invalid Handle Response.
|
|
|
|
|
| |
Verify that a Generic Attribute Profile server can support writing
a long Characteristic Value selected by handle.
|
|
|
|
|
|
| |
Verify that a Generic Attribute Profile server can detect and
reject a Write Characteristic Descriptor Request to a non-writeable
characteristic descriptor and issue a Write Not Permitted Response.
|
|
|
|
|
|
| |
Verify that a Generic Attribute Profile server can detect a Write
Characteristic Descriptor Request with an unsupported characteristic
descriptor handle and issue an Invalid Handle Response.
|
|
|
|
|
| |
Verify that a Generic Attribute Profile server can support writing
a characteristic descriptor selected by handle.
|
|
|
|
|
| |
This checks if crypto is enabled and in case it is not do not run test
/TP/GAW/CL/BV-02-C.
|
|
|
|
|
| |
Generic Attribute Profile client behavior when the Write Characteristic
Descriptor procedure fails due to insufficient encryption key size.
|
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the Write
Characteristic Descriptor procedure fails due to insufficient
authentication.
|
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the Write
Characteristic Descriptor procedure fails due to insufficient
authorization.
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the Write
Characteristic Descriptor procedure fails due to write not permitted.
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the Write
Characteristic Descriptor procedure fails due to invalid handle.
|
|
|
|
|
| |
Verify that a Generic Attribute Profile client can write a
characteristic descriptor selected by handle.
|
|
|
|
|
| |
The GATT server test cases are supposed to be tested against
ts_small_db and ts_large_db_1. So, Fixed these changes too.
|
|
|
|
|
| |
The GATT server test cases are supposed to be tested against
ts_small_db and ts_large_db_1. So, Fixed those changes too.
|
|
|
|
|
| |
The GATT server test cases are supposed to be tested against
ts_small_db and ts_large_db_1. So, Fixed those changes too.
|
|
|
|
|
|
| |
This patch adds code to clean up pending discovery requests in
unit/test-gatt, since the recent API changes will cause memory leaks
otherwise.
|
|
|
|
|
|
| |
Verify that a Generic Attribute Profile server can detect and
reject a Write Characteristic Value Request to a non-writeable
Characteristic Value and issue a Write Not Permitted Response.
|
|
|
|
|
|
| |
Verify that a Generic Attribute Profile server can detect a Write
Characteristic Value Request with an unsupported Characteristic
Value handle and issue an Invalid Handle Response.
|
|
|
|
|
| |
Verify that a Generic Attribute Profile server can support writing
a Characteristic Value selected by handle.
|
|
|
|
|
| |
This add a test for signed write but with security level other than low
so we can verify the code use the write instead of signed write.
|
|
|
|
|
| |
Verify that a Generic Attribute Profile client can write a
characteristic with authentication without response.
|
|
|
|
|
| |
Verify that a Generic Attribute Profile client can issue a
characteristic Write without response.
|
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the Write
Characteristic Value procedure fails due to insufficient encryption
key size.
|
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the
Write Characteristic Value procedure fails due to insufficient
authentication.
|
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the
Write Characteristic Value procedure fails due to insufficient
authorization.
|
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the
Write Characteristic Value procedure fails due to write
not permitted.
|
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the
Write Characteristic Value procedure fails due to invalid
handle.
|
|
|
|
|
| |
Verify that a Generic Attribute Profile client can write a
Characteristic Value selected by handle.
|
|
|
|
| |
Our tester framework actually produces much better output.
|
|
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when an attempt to use
LE transport to execute the Read Characteristic Value procedure on a
characteristic contained within a service defined for use only over
BR/EDR transport.
|
|
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when an attempt to use
BR/EDR transport to execute the Read Characteristic Value procedure on a
characteristic contained within a service defined for use only over
LE transport.
|
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the Read Long
Characteristic Descriptor procedure fails due to insufficient encryption
key size.
|
|
|
|
|
|
| |
Verify Generic Attribute Profile client behavior when the Read Long
Characteristic Descriptor procedure fails due to insufficient
authentication.
|