tree: 81ce78cdf74d0fda7d07cd375ac4484ff66ac4d4 [path history] [tgz]
  1. BUILD.gn
  2. README.md
  3. component_base.h
  4. component_context_fake.cc
  5. component_context_fake.h
  6. component_main.h
  7. entity_resolver_fake.cc
  8. entity_resolver_fake.h
  9. fake_agent_runner_storage.h
  10. ledger_repository_for_testing.cc
  11. ledger_repository_for_testing.h
  12. mock_base.cc
  13. mock_base.h
  14. module_facet_reader_fake.cc
  15. module_facet_reader_fake.h
  16. module_resolver_fake.cc
  17. module_resolver_fake.h
  18. session_shell_base.h
  19. session_shell_impl.cc
  20. session_shell_impl.h
  21. story_controller_mock.h
  22. story_provider_mock.h
  23. test_driver.h
  24. test_story_command_executor.cc
  25. test_story_command_executor.h
  26. test_with_ledger.cc
  27. test_with_ledger.h
  28. test_with_session_storage.cc
  29. test_with_session_storage.h
  30. wait_until_idle.h
peridot/lib/testing/README.md

Here is code that helps clients of modular with testing.

When linked against the //peridot/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.