tree: a25f40c11bbfe7d92f57d0c9b5b3d85b0ffbd2c0 [path history] [tgz]
  1. BUILD.gn
  2. client_gen_api_test.cc
  3. flexible.test.fidl
  4. flexible_test.cc
  5. handle_raii.test.fidl
  6. handle_raii_test.cc
  7. handle_rights.test.fidl
  8. handle_rights_test.cc
  9. llcpp.test.fidl
  10. protocol.test.fidl
  11. protocol_test.cc
  12. README.md
  13. server_gen_api_test.cc
  14. transitional.test.fidl
  15. transitional_test.cc
src/lib/fidl/llcpp/tests/integration/README.md

Integration tests

These tests verify that the various components of LLCPP work together to deliver a particular feature. For example, handle_rights_test.cc tests that the client and server dispatchers verify handle type and down-scope handle rights. flexible_test.cc tests that LLCPP over-allocates memory for flexible types, in anticipation of receiving unknown fields pushing the message over its statically computed size limit.

It's good to have a few end-to-end tests verifying the behavior at a high level, but we should prefer writing tests with a more granular coverage, and over a smaller interface, such that the resulting tests are easier to setup and interpret, acknowledging the gap in the status quo.