tree: a704e9229cb962eff9adff0edf05e6f543a225d6 [path history] [tgz]
  1. BUILD.gn
  2. component_base.h
  3. component_main.h
  4. ledger_repository_for_testing.cc
  5. ledger_repository_for_testing.h
  6. mock_base.cc
  7. mock_base.h
  8. README.md
  9. session_shell_base.h
  10. session_shell_impl.cc
  11. session_shell_impl.h
  12. story_controller_mock.h
  13. story_provider_mock.h
  14. test_driver.h
  15. test_story_command_executor.cc
  16. test_story_command_executor.h
  17. test_with_ledger.cc
  18. test_with_ledger.h
  19. test_with_session_storage.cc
  20. test_with_session_storage.h
  21. wait_until_idle.h
src/modular/lib/testing/README.md

Here is code that helps clients of modular with testing.

When linked against the //src/modular/lib/testing library target, a test application can use the functions in lib/testing/testing.h to interact with the TestRunner service in its environment. This is the standard way to test multi-process modular applications; these functions allow a test to declare failure, and signal tear down of tests to the TestRunner service.

See //peridot/tests for more details on running tests.