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

..--

att/23-Nov-2023-188117

btaa/23-Nov-2023-1,7031,266

cert/23-Nov-2023-6,7365,040

common/23-Nov-2023-4,8323,209

crypto_toolbox/23-Nov-2023-1,9651,338

docs/23-Nov-2023-1,061822

dumpsys/23-Nov-2023-3,4292,437

facade/23-Nov-2023-578409

fuzz/23-Nov-2023-15899

grpc/23-Nov-2023-295164

hal/23-Nov-2023-2,9692,170

hci/23-Nov-2023-29,42823,395

iso/23-Nov-2023-1,4491,078

l2cap/23-Nov-2023-22,75316,037

neighbor/23-Nov-2023-3,2702,333

os/23-Nov-2023-7,5465,078

packet/23-Nov-2023-16,22611,434

proto/23-Nov-2023-400318

rust/23-Nov-2023-9,4857,586

security/23-Nov-2023-13,3789,533

shim/23-Nov-2023-892571

storage/23-Nov-2023-4,1122,901

.clang-formatD23-Nov-20231 KiB3229

.gitignoreD23-Nov-202348 43

Android.bpD23-Nov-202328.8 KiB1,000967

Android.mkD23-Nov-20235.4 KiB10788

AndroidTestTemplate.xmlD23-Nov-20231.7 KiB3722

BUILD.gnD23-Nov-20233.3 KiB135116

README.mdD23-Nov-2023919 2817

benchmark.ccD23-Nov-2023848 268

dumpsys_data.fbsD23-Nov-2023953 2621

fuzz_test.ccD23-Nov-20231.1 KiB2911

module.ccD23-Nov-20235.7 KiB168119

module.hD23-Nov-20236.3 KiB237157

module_unittest.ccD23-Nov-20239.7 KiB321218

module_unittest.fbsD23-Nov-2023157 117

module_unittest_generated.hD23-Nov-20233.1 KiB8567

setup.pyD23-Nov-20233.8 KiB11474

stack_manager.ccD23-Nov-20232.9 KiB10464

stack_manager.hD23-Nov-20231.3 KiB5126

stack_manager_unittest.ccD23-Nov-20231.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