tree: bc63ccbc094f124e78e9dd3768518c93a53323ff [path history] [tgz]
  1. meta/
  2. modular_config/
  3. agent_services_test.cc
  4. agent_session_restart_test.cc
  5. BUILD.gn
  6. component_context_test.cc
  7. inspect_session_test.cc
  8. intents_test.cc
  9. intl_property_provider_test.cc
  10. intl_property_provider_test_client.h
  11. last_focus_time_test.cc
  12. login_override_test.cc
  13. module_context_test.cc
  14. module_with_fake_runner.cc
  15. README.md
  16. session_shell_test.cc
  17. sessionctl_test.cc
  18. sessionmgr_integration_test.cc
  19. stories_share_session_runners_test.cc
  20. story_module_test.cc
  21. story_shell_embedded_mod_test.cc
  22. story_shell_factory_test.cc
  23. story_shell_test.cc
  24. test_service.test.fidl
src/modular/tests/README.md

Integration tests

Integration tests are written against client-facing FIDL services exposed by Modular. They make use of the Modular Test Harness.

Writing a new test

The easiest way to get started is to make a copy of an existing test. Be sure to:

  1. Add an entry in BUILD.gn to build the new test executable()
  2. Create a .cmx meta file in meta/
  3. Add both the executable binary to the test_package() declaration in BUILD.gn

Running tests

Run the following commands to build & run your tests:

fx set core.x64 --with //src/modular/tests
fx build

NOTE: You only need to run fx set once.

Running all tests

fx run-test modular_integration_tests

Running one test

Add the following to the above command:

-- --gtest_filter="{ClassName}.{TestName}"