• Home
Name Date Size #Lines LOC

..--

att/03-May-2024-191118

btaa/03-May-2024-1,9991,495

cert/03-May-2024-1,126893

common/03-May-2024-5,9073,913

crypto_toolbox/03-May-2024-1,9651,338

docs/03-May-2024-1,063824

dumpsys/03-May-2024-3,6132,562

facade/03-May-2024-514355

fuzz/03-May-2024-15899

grpc/03-May-2024-294163

hal/03-May-2024-3,3792,534

hci/03-May-2024-36,39329,221

iso/03-May-2024-1,018725

l2cap/03-May-2024-19,18813,199

metrics/03-May-2024-990712

neighbor/03-May-2024-3,0272,165

os/03-May-2024-8,3775,671

packet/03-May-2024-17,40412,323

proto/03-May-2024-401319

rust/03-May-2024-25,47720,290

security/03-May-2024-11,2747,991

shim/03-May-2024-803530

storage/03-May-2024-4,6973,386

.clang-formatD03-May-20241 KiB3229

.gitignoreD03-May-202448 43

Android.bpD03-May-202426.1 KiB918886

AndroidTestTemplate.xmlD03-May-20242.3 KiB4629

BUILD.gnD03-May-20243.7 KiB142123

README.mdD03-May-2024919 2817

benchmark.ccD03-May-2024848 268

dumpsys_data.fbsD03-May-20241.3 KiB3831

fuzz_test.ccD03-May-20241.1 KiB2911

module.ccD03-May-20245.7 KiB168119

module.hD03-May-20246.3 KiB237157

module_unittest.ccD03-May-20249.7 KiB319216

module_unittest.fbsD03-May-2024157 117

module_unittest_generated.hD03-May-20243.1 KiB8567

stack_manager.ccD03-May-20242.7 KiB9457

stack_manager.hD03-May-20241.3 KiB5025

stack_manager_unittest.ccD03-May-20241.8 KiB6035

README.md

1### Why is gabeldorsche plural?
2
3Please see this [informative video we've prepared](https://www.youtube.com/watch?v=vLRyJ0dawjM).
4
5### Architecture
6
7Guidelines for developing the Gabeldorsche (GD) stack
8
9*   [Architecture](./docs/architecture/architecture.md)
10*   [Style Guide](./docs/architecture/style_guide.md)
11
12### Testing
13
14Gabeldorsche (GD) was built with test driven development in mind. Three types of
15tests are used in ensuring Gabeldorsche stack's stability, correctness and free
16from regression.
17
18If you are verifying something is glued or hooked up correctly inside the stack,
19use a unit test.
20
21*   [GTest Unit Test](./docs/testing/gtest.md)
22
23If you are verifying correct behavior (especially interop problems) **DO NOT**
24write a unit test as this not a good use of your time. Write a [cert test](./cert_test.md) instead
25so it applies to any stack.
26
27*   [GD Certification Tests](./docs/testing/cert_test.md)
28