• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..--

att/23-Mar-2024-15689

cert/23-Mar-2024-5,2453,890

common/23-Mar-2024-3,1812,091

crypto_toolbox/23-Mar-2024-1,9231,303

docs/23-Mar-2024-1,061822

dumpsys/23-Mar-2024-2,9822,110

facade/23-Mar-2024-544381

fuzz/23-Mar-2024-14991

grpc/23-Mar-2024-295164

hal/23-Mar-2024-2,1461,528

hci/23-Mar-2024-22,97817,748

l2cap/23-Mar-2024-20,65314,501

neighbor/23-Mar-2024-3,1472,237

os/23-Mar-2024-4,9123,299

packet/23-Mar-2024-13,6379,280

proto/23-Mar-2024-372294

security/23-Mar-2024-10,5847,357

shim/23-Mar-2024-2,1631,561

storage/23-Mar-2024-4,0372,840

.clang-formatD23-Mar-20241 KiB3229

Android.bpD23-Mar-202421.8 KiB754727

Android.mkD23-Mar-20245.1 KiB10084

AndroidTestTemplate.xmlD23-Mar-20241.7 KiB3722

README.mdD23-Mar-2024919 2817

TEST_MAPPINGD23-Mar-2024251 1716

benchmark.ccD23-Mar-2024848 268

dumpsys_data.fbsD23-Mar-2024346 1611

fuzz_test.ccD23-Mar-20241.1 KiB2911

module.ccD23-Mar-20244.9 KiB155107

module.hD23-Mar-20246.3 KiB236156

module_unittest.ccD23-Mar-20249.2 KiB300202

module_unittest.fbsD23-Mar-2024157 117

module_unittest_generated.hD23-Mar-20243.1 KiB8567

setup.pyD23-Mar-20243.8 KiB11373

stack_manager.ccD23-Mar-20242.3 KiB7544

stack_manager.hD23-Mar-20241.2 KiB4521

stack_manager_unittest.ccD23-Mar-20241.7 KiB5732

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