tree: e3cefe1189f5c7cfb690ddd5437ab9be8ff28fd9 [path history] [tgz]
  1. BUILD.gn
  2. component_base.h
  3. component_main.h
  4. entity_resolver_fake.cc
  5. entity_resolver_fake.h
  6. ledger_repository_for_testing.cc
  7. ledger_repository_for_testing.h
  8. mock_base.cc
  9. mock_base.h
  10. module_facet_reader_fake.cc
  11. module_facet_reader_fake.h
  12. module_resolver_fake.cc
  13. module_resolver_fake.h
  14. README.md
  15. session_shell_base.h
  16. session_shell_impl.cc
  17. session_shell_impl.h
  18. story_controller_mock.h
  19. story_provider_mock.h
  20. test_driver.h
  21. test_story_command_executor.cc
  22. test_story_command_executor.h
  23. test_with_ledger.cc
  24. test_with_ledger.h
  25. test_with_session_storage.cc
  26. test_with_session_storage.h
  27. 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.