tree: 8dd69e92b64e3846810c0820a9bb92bfc21ad7a9 [path history] [tgz]
  1. BUILD.gn
  2. README.md
  3. component_base.h
  4. component_main.h
  5. session_shell_base.h
  6. session_shell_impl.cc
  7. session_shell_impl.h
  8. test_driver.h
  9. test_story_command_executor.cc
  10. test_story_command_executor.h
  11. test_with_session_storage.cc
  12. test_with_session_storage.h
  13. 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.