History log of /external/autotest/client/site_tests/touch_TouchscreenScroll/touch_TouchscreenScroll.py
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
79c9661b16ba8507f3f57bd8dba7cd3d0c2db7ef 29-Dec-2015 pramod <pbathini@chromium.org> Updating touch_playback_test_base.py for better error handling

Added try block for default scroll function, called the wait_for
default_scroll() in try block and removed it from three others files
it was present.Seperated the set_scroll() function into its own function
and called it inside the try block.

BUG=chromium:554680
TEST=tested on Daisy and Alex

Change-Id: I503dc647f05b859c292bd4025edfef147467d0a3
Reviewed-on: https://chromium-review.googlesource.com/319644
Commit-Ready: Pramod Bathini <pbathini@chromium.org>
Tested-by: Pramod Bathini <pbathini@chromium.org>
Reviewed-by: Mussa Kiroga <mussa@chromium.org>
/external/autotest/client/site_tests/touch_TouchscreenScroll/touch_TouchscreenScroll.py
d123d72c5c9f4edbd91ce4f20432a40c55773707 28-Oct-2015 Katherine Threlkeld <kathrelkeld@chromium.org> [Autotest] Add device id to touch_* test gesture filenames.

As more and more platforms have touchpads and touchscreens
sourced from several companies, identify recorded gesture
files with the hardware id of the device in order to
differentiate.

This change will prevent bugs like the one where the Cypress
daisy files failed on Atmel daisy.

Renames all device files to have the same format:
<platform>_<input type>_<hwid>_<gesture-name>

Also make all tests with per-platform gestures use the same
common code to find these renamed gesture files.

Finally, this change restructures how device infomation is
saved by adding a device class with the pertinant information.
We now find the hardware and firmware ids (if present) and
save them in this new class, along with the previously found
node, name, and folder path.

Now output firmware and hardware info in all tests for debugging.

TEST=ran all affected tests across several devices
BUG=chromium:488282

Change-Id: I5d331d354fcfdc3c4d44a9b8a4a3ac97bd04981b
Reviewed-on: https://chromium-review.googlesource.com/309360
Commit-Ready: Katherine Threlkeld <kathrelkeld@chromium.org>
Tested-by: Katherine Threlkeld <kathrelkeld@chromium.org>
Reviewed-by: Mussa Kiroga <mussa@chromium.org>
/external/autotest/client/site_tests/touch_TouchscreenScroll/touch_TouchscreenScroll.py
8d956e1a0de95d3e5188a2eb948afddaafe4908f 29-Sep-2015 Katherine Threlkeld <kathrelkeld@chromium.org> Autotest: add new touchscreen playback autotests.

Add touchscreen versions of the existing touchpad taps and scroll
tests. These tests will run on touchscreen devices (though only
Samus for right now).

touch_TouchscreenTaps plays back a touchscreen tap and ensures
that Chrome saw a mouse click.

touch_TouchscreenScroll plays back one-finger scrolls in four
different directions, ensuring that Chrome interprets this scroll
in the correct direction.

TEST=passed on Samus
BUG=None
CQ-DEPEND=302690

Change-Id: I48bbf17a2a6e39f186a0d8a8966078f93e07738c
Reviewed-on: https://chromium-review.googlesource.com/302873
Commit-Ready: Katherine Threlkeld <kathrelkeld@chromium.org>
Tested-by: Katherine Threlkeld <kathrelkeld@chromium.org>
Reviewed-by: David Haddock <dhaddock@chromium.org>
/external/autotest/client/site_tests/touch_TouchscreenScroll/touch_TouchscreenScroll.py