tree: 800091b71d69318df0b96651b68feb736977fae7 [path history] [tgz]
  1. BUILD.gn
  2. client_gen_api_test.cc
  3. dispatcher_handle_ownership.test.fidl
  4. dispatcher_handle_ownership_test.cc
  5. flexible.test.fidl
  6. flexible_test.cc
  7. handle_raii.test.fidl
  8. handle_raii_test.cc
  9. handle_rights.test.fidl
  10. handle_rights_test.cc
  11. llcpp.test.fidl
  12. protocol.test.fidl
  13. protocol_test.cc
  14. README.md
  15. server_gen_api_test.cc
  16. sync_client_error_tests.cc
  17. transitional.test.fidl
  18. transitional_test.cc
  19. v2_integration.test.fidl
  20. v2_integration_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.