Google Git
Sign in
chromium / chromiumos / platform / touchpad-tests / refs/heads/stabilize-15572.16.B
commit6a1a3f5aa8dfa163e0506363c99626e05d51b01e[log] [tgz]
authorSean O'Brien <seobrien@chromium.org>Tue May 09 17:54:38 2023
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon May 15 21:10:35 2023
tree2b57096aeafd6c330030f6a0df3c9b9cdc6eb997
parent80639bc303f6687ad824a1828f6e7a30af0cd62b [diff]
Add test for tap-drag failure on redrix

This test includes a recording from a failure in the field where the
user taps, pauses, then moves the cursor.  This should be interpreted as
a tap and then a move, not a tap-drag gesture.

BUG=b:231621332, b:231355042
TEST=Check that failure is not seen after gesture library fix is applied

Change-Id: I0118c4969654417862997852cdc640eca4016571
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/touchpad-tests/+/4529017
Commit-Queue: Sean O'Brien <seobrien@chromium.org>
Tested-by: Sean O'Brien <seobrien@chromium.org>
Reviewed-by: Denis Brockus <dbrockus@chromium.org>
3 files changed
tree: 2b57096aeafd6c330030f6a0df3c9b9cdc6eb997
  1. framework/
  2. tests/
  3. .gitignore
  4. DIR_METADATA
  5. Makefile
  6. OWNERS
  7. README.md
  8. touchtests
  9. touchtests.template
  10. unblocked_terms.txt
README.md

Touch tests

Introduction

This repository contains automated tests for Chromium OS's Gestures library. Each test has a log of evdev events which are replayed, a properties file containing gesture properties to set while the Gestures library runs, and a Python function which verifies the output and returns a test score.

Setting up

Assuming that you've followed the developer guide, simply run the following inside your chroot:

(inside)
$ cd ~/trunk/src/platform/touchpad-tests
$ sudo make setup-in-place

Running tests

To run all tests, simply run touchtests. To run one or more specific tests, you can pass a test name or a glob:

(inside)
$ touchtests atlas-1.0/fat-thumb-fail
$ touchtests atlas-1.0/palm-while-typing*

Each test will return a status, with the following meanings:

  • success: the test succeeded, with the given score out of 1.
  • failure: the test failed.
  • error: an error occurred while running the test, so the behavior of the gestures library couldn't be evaluated.
  • incomplete: (baseline tests only) the evdev log for this platform hasn't been created.

Checking for regressions

The --out (or -o) switch creates a report file that future runs can be compared against with the --ref (or -r) switch:

(inside)
$ touchtests --out baseline.json
# (cause some regressions)
$ touchtests --ref baseline.json

The output table will contain a delta column that indicates any regressions or improvements, and an error message will be shown if regressions exist.