| commit | 80639bc303f6687ad824a1828f6e7a30af0cd62b | [log] [tgz] |
|---|---|---|
| author | Sean O'Brien <[email protected]> | Tue Nov 08 22:20:03 2022 |
| committer | Chromeos LUCI <[email protected]> | Tue Nov 22 18:55:56 2022 |
| tree | 765abfbc0f47a72fd849fda5d38a86cb0631f7e1 | |
| parent | 3433889ac7a3756e6166332a33ab7d10ac676d5a [diff] |
Add initial MSC_TIMESTAMP field for existing tests When tests were originally added for devices which report the MSC_TIMESTAMP field, MTReplay did not include the initial value in the evdev log. This CL retroactively adds an initial value to affected tests. Also, modify the expected movement distance for one test where this adjustment caused a "false regression". After manually reviewing the regressed test, there was only a slight adjustment to movement distance, but the test passed qualitatively. BUG=b:258267647 TEST=run touchtests Change-Id: If0a7f373dd49925104c0f3cb19f963f4bbf33f29 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/touchpad-tests/+/4014629 Commit-Queue: Sean O'Brien <[email protected]> Tested-by: Sean O'Brien <[email protected]> Reviewed-by: Denis Brockus <[email protected]>
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.