tree: ee91bc5f8374ab42505340577176159e06a94db2 [path history] [tgz]
  4. component_manager/
  5. element_management/
  6. examples/
  7. realm_management/
  8. session_manager/
  9. session_manager_integration_tests/

Session Manager Usage Guide

Build a configuration that boots into a session

fx set core.x64 --with-base=//src/session:session_framework,//src/session:examples,//src/session/session_manager:session_manager.config,//src/ui/scenic:scenic_pkg
fx build
fx reboot

Specify which session to launch in session_manager.cml:

"args": [ "-s", "fuchsia-pkg://" ],

To launch a session manually (e.g., if you don't include session_manager.config in --with-base) you can run the following command:

fx shell run fuchsia-pkg:// fuchsia-pkg://

TODO(37237): Multiple calls to run will not work correctly when launching graphical sessions (“display has been claimed by another compositor” - Scenic). This will be resolved by introducing a command line tool for launching sessions “properly.”

To run the tests

Run fx shell ifconfig to find the IP address of the device that will run the test.

Use the following command to launch the set of Session Framework tests defined in test_plan.json. Tests listed in test_plan.json can be v1 or v2 components. Every test included in this list needs to expose /svc/fuchsia.test.Suite.

This command starts the test_runner which uses component_manager to launch each test as a component. Note that these tests are not run in CQ.

FUCHSIA_IPV4_ADDR=<IP OF DEVICE> FUCHSIA_SSH_KEY=.ssh/pkey ./out/default/host_x64/dart-tools/test_runner -p src/session/session_manager_integration_tests/test_plan.json

Debug tips

If the test hangs after these lines:

creating sl4f driver
starting sl4f driver

you may need to reconfigure your network setup.