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