android13/packages/modules/Bluetooth/system/gd
liiir1985 7f62dcda9f initial 2024-06-22 20:45:49 +08:00
..
att initial 2024-06-22 20:45:49 +08:00
btaa initial 2024-06-22 20:45:49 +08:00
cert initial 2024-06-22 20:45:49 +08:00
common initial 2024-06-22 20:45:49 +08:00
crypto_toolbox initial 2024-06-22 20:45:49 +08:00
docs initial 2024-06-22 20:45:49 +08:00
dumpsys initial 2024-06-22 20:45:49 +08:00
facade initial 2024-06-22 20:45:49 +08:00
fuzz initial 2024-06-22 20:45:49 +08:00
grpc initial 2024-06-22 20:45:49 +08:00
hal initial 2024-06-22 20:45:49 +08:00
hci initial 2024-06-22 20:45:49 +08:00
iso initial 2024-06-22 20:45:49 +08:00
l2cap initial 2024-06-22 20:45:49 +08:00
metrics initial 2024-06-22 20:45:49 +08:00
neighbor initial 2024-06-22 20:45:49 +08:00
os initial 2024-06-22 20:45:49 +08:00
packet initial 2024-06-22 20:45:49 +08:00
proto initial 2024-06-22 20:45:49 +08:00
rust initial 2024-06-22 20:45:49 +08:00
security initial 2024-06-22 20:45:49 +08:00
shim initial 2024-06-22 20:45:49 +08:00
storage initial 2024-06-22 20:45:49 +08:00
.clang-format initial 2024-06-22 20:45:49 +08:00
.gitignore initial 2024-06-22 20:45:49 +08:00
Android.bp initial 2024-06-22 20:45:49 +08:00
AndroidTestTemplate.xml initial 2024-06-22 20:45:49 +08:00
BUILD.gn initial 2024-06-22 20:45:49 +08:00
README.md initial 2024-06-22 20:45:49 +08:00
benchmark.cc initial 2024-06-22 20:45:49 +08:00
dumpsys_data.fbs initial 2024-06-22 20:45:49 +08:00
fuzz_test.cc initial 2024-06-22 20:45:49 +08:00
module.cc initial 2024-06-22 20:45:49 +08:00
module.h initial 2024-06-22 20:45:49 +08:00
module_unittest.cc initial 2024-06-22 20:45:49 +08:00
module_unittest.fbs initial 2024-06-22 20:45:49 +08:00
module_unittest_generated.h initial 2024-06-22 20:45:49 +08:00
stack_manager.cc initial 2024-06-22 20:45:49 +08:00
stack_manager.h initial 2024-06-22 20:45:49 +08:00
stack_manager_unittest.cc initial 2024-06-22 20:45:49 +08:00

README.md

Why is gabeldorsche plural?

Please see this informative video we've prepared.

Architecture

Guidelines for developing the Gabeldorsche (GD) stack

Testing

Gabeldorsche (GD) was built with test driven development in mind. Three types of tests are used in ensuring Gabeldorsche stack's stability, correctness and free from regression.

If you are verifying something is glued or hooked up correctly inside the stack, use a unit test.

If you are verifying correct behavior (especially interop problems) DO NOT write a unit test as this not a good use of your time. Write a cert test instead so it applies to any stack.