| commit | ec8fc231e199b16c4d1a247853c9afc17d297402 | [log] [tgz] |
|---|---|---|
| author | Jora Jacobi <jora@google.com> | Mon May 11 22:07:46 2020 |
| committer | Commit Bot <commit-bot@chromium.org> | Thu May 28 23:35:01 2020 |
| tree | 7a0ac90ce1d88bf661f0dfc6ad457e10e87c6b96 | |
| parent | e70279edcc395d6f6ce438ce131e0b02f64a3d25 [diff] |
Add tests to validate scroll behavior on BT mouse Certain BT mice (such as Microsoft Surface Precision mouse) had an issue where scroll behavior was unpredictable on mouse wakeup. Add two tests to validate the fix to this behavior: - jerky_scroll ensures that slow, intermittent scrolling (which initially triggered the bad behavior) would give the amount of scroll expected - fast_scroll ensures that the fix doesn't have a negative impact when the user is trying to scroll rapidly BUG=b:149932225 TEST=Ensure all current and new touchtests pass (src/platform/touchpad-tests) Cq-Depend: chromium:2195473, chromium:2197189 Change-Id: I736ebd912b812fdf6eecbdb8b66aa1580991bc15 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/touchpad-tests/+/2195185 Reviewed-by: Harry Cutts <hcutts@chromium.org> Reviewed-by: Jora Jacobi <jora@google.com> Reviewed-by: Sean O'Brien <seobrien@chromium.org> Tested-by: Jora Jacobi <jora@google.com> Commit-Queue: Jora Jacobi <jora@google.com>
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.
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
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:
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.