tree: 748e7809b80bbbf249dfd647261982fd45957b90 [path history] [tgz]
  1. meta/
  2. touch-flatland-client/
  3. BUILD.gn
  4. pointerinjector-config-test.cc
  5. README.md
  6. touch-input-test.cc
src/ui/tests/integration_input_tests/touch/README.md

Build the test

$ fx set <product>.<arch> --with //src/ui/tests/integration_input_tests/touch:tests

Run the test

To run the fully-automated test, use this fx invocation:

$ fx test touch-input-test

To see extra logs:

$ fx test --min-severity-logs=DEBUG touch-input-test -- --verbose=2

Add trace metrics to the test

This test suite uses the category touch-input-test to log trace events. Any new categories added to a test will need to be included in the fx traceutil record command below.

Trace event types can be found in libtrace.

Record a trace of the test

Add the tracing package to your fx set:

$ fx set <product>.<arch> --with //src/ui/tests/integration_input_tests/touch:tests --with-base=//bundles/packages/prod:tracing

To record a trace of the test, use this fx invocation:

$ fx traceutil record --duration 20s --categories touch-input-test fuchsia-pkg://fuchsia.com/touch-input-test#meta/touch-input-test.cm

Note: The default duration for traceutil record is 10 seconds. When running locally, package resolving can take more than 10 seconds. If the recording ends before the test completes, increase the amount of time in the --duration flag.

Play with clients

You can use tiles-session to manually run and interact with any of the child clients under test.

Play with the C++ Flatland client

To play around with the C++ Flatland client used in the automated test, invoke the client like this:

$ ffx session add fuchsia-pkg://fuchsia.com/touch-flatland-client#meta/touch-flatland-client.cm

Play with the web client

To play around with the web client used in the automated test, invoke the client like this:

$ ffx session add fuchsia-pkg://fuchsia.com/one-chromium#meta/one-chromium.cm