tree: 9f961f98490d6b0825bdbefdda68965691b8d6eb [path history] [tgz]
  1. .clang-format
  2. .gitignore
  3. Android.bp
  4. Android.mk
  5. AndroidTestTemplate.xml
  6. BUILD.gn
  7. README.md
  8. att/
  9. benchmark.cc
  10. btaa/
  11. cert/
  12. common/
  13. crypto_toolbox/
  14. docs/
  15. dumpsys/
  16. dumpsys_data.fbs
  17. facade/
  18. fuzz/
  19. fuzz_test.cc
  20. grpc/
  21. hal/
  22. hci/
  23. iso/
  24. l2cap/
  25. module.cc
  26. module.h
  27. module_unittest.cc
  28. module_unittest.fbs
  29. module_unittest_generated.h
  30. neighbor/
  31. os/
  32. packet/
  33. proto/
  34. rust/
  35. security/
  36. setup.py
  37. shim/
  38. stack_manager.cc
  39. stack_manager.h
  40. stack_manager_unittest.cc
  41. storage/
gd/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.