pyformat run_test. No code changes.

Change-Id: Iaf525f2e6f772226763d0f1d2d68b59c70cfc0e0
1 file changed
tree: f77c4207f176707c07f24b8f51b0a07d8090b2f7
  1. .clang-format
  2. .gitignore
  3. .travis.yml
  9. docs/
  10. examples/
  11. infra/
  12. lib/
  13. services/
  14. src/
  15. tests/


Modular provides a framework for ephemerally downloaded applications which may have been implemented in different programming languages to run in a shared context and provide a composed experience to the user. The framework is also responsible for application lifecycle, resource management, view hierarchy, authentication, etc.


  1. Follow instructions in fuchsia for getting the source, setup, build and running Fuchsia.
  2. Follow instructions in ledger to setup the Ledger and all its dependencies including netstack and minfs.


On the Fuchsia command line you can start an example application flow like this:

device_runner --user_shell=dummy_user_shell

A single application can be run using the dev_user_shell, for example:

device_runner --user_shell=dev_user_shell --user_shell_args='--root_module=example_flutter_counter_parent,--root_link={"":5}'

Note: if you are running this through netruncmd you will need to escape the quotes:

device_runner --user_shell=dev_user_shell --user_shell_args='--root_module=example_flutter_counter_parent,--root_link={\\\"\\\":5}'

The flags --user_shell and --user_shell_args are read by device_runner. The value of --user_shell is the application run as user shell. The value of --user_shell_args is a comma separated list of arguments passed to the user shell application. In this example, these arguments are in turn more flags. Commas inside the value of such arguments are escaped by backslashes. The value of --root_module selects the module to run. The value of --root_link is a JSON representation of the initial data the module is started with.

The dummy user name used by the dummy user shell can be set with --user:

device_runner --user_shell=dummy_user_shell --user_shell_args=--user=dummy_user

Applications are generally referenced by URLs. If the application binary is in a location where application manager expects it (specifically /system/apps) the URL can be relative. Otherwise, the URL should be relative with an absolute path, or absolute altogether. For example (from test runner invocation):

device_runner --user_shell=dev_user_shell --user_shell_args=--root_module=/tmp/tests/parent_child/parent_module

or even more generally:

device_runner --user_shell=dev_user_shell --user_shell_args=--root_module=file:///tmp/tests/parent_child/parent_module