To run modules from the command line, you need to modify the startup behavior of Fuchsia to prevent device_runner and Armadillo from starting by default. Use fx set and build as shown below:
fx set x64 --packages peridot/packages/products/test_modular fx full-build
(If fx is not in your PATH, you should add .jiri_root/bin to your PATH.)
Note: The command lines in this section are only examples. Most of them will hang if you try to execute them because they require test_runner to also be running on the Fuchsia device.
You can start the basic test application like this.
device_runner --account_provider=dev_token_manager \ --device_shell=dev_device_shell --user_shell=test_user_shell \ --story_shell=dev_story_shell
A single application can be run using dev_user_shell. For example, to run example_flutter_counter_parent_story_shell, use this command:
device_runner --account_provider=dev_token_manager \ --device_shell=dev_device_shell --user_shell=dev_user_shell \ --user_shell_args='--root_module=example_flutter_counter_parent_story_shell' \ --story_shell=dev_story_shell
dev_device_shell is used to log in a dummy user directly without going through an authentication dialog. test_user_shell runs the test.
Note: When running commands with fx shell, you will need to double-escape the quotes.
fx shell \ "device_runner --device_shell=dev_device_shell --user_shell=dev_user_shell \ --user_shell_args='--root_module=example_flutter_counter_parent_story_shell,--root_link={\\\"http://schema.domokit.org/counter\\\":5}' \ --story_shell=dev_story_shell"
The flags --user_shell and --user_shell_args are read by device_runner. The value of --user_shell is the application that is run as the 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 user name provided by dev_device_shell can be set with --user. It is used by device_runner when opening the Ledger. However, the --user parameter does not work for userpicker_device_shell:
device_runner --account_provider=dev_token_manager \ --device_shell=dev_device_shell --device_shell_args=--user=dummy_user \ --user_shell=test_user_shell --story_shell=dev_story_shell
Applications are generally referenced by URLs. If the application binary is in a location where application manager expects it (e.g., /system/bin) 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 --test --account_provider=dev_token_manager \ --device_shell=dev_device_shell --user_shell=dev_user_shell \ --story_shell=dev_story_shell \ --user_shell_args=--root_module=/system/test/modular_tests/parent_child_test_parent_module
or even more generally:
device_runner --test --account_provider=dev_token_manager \ --device_shell=dev_device_shell --user_shell=dev_user_shell \ --story_shell=dev_story_shell \ --user_shell_args=--root_module=file:///system/test/modular_tests/parent_child_test_parent_module
