tree: a4f16127d83a461a56b8b5586006d2f3a982bbc8 [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 touch tests to the base package set:

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

```shell
$ ffx trace start --categories touch-input-test --background
$ fx test touch-input-test
$ ffx trace stop

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