| 6c5d54211c27cfbc0018e57a677cc3c1deb1f946 |
|
21-May-2014 |
Joseph Hwang <josephsih@chromium.org> |
firmware_TouchMTB: Remove dependency on Xlib
It looks like python-xlib is no longer getting included in the test
images. Fortunately, the functionality of Xlib has been replaced
gradually. This patch completely removes the dependency on Xlib.
BUG=chromium:375518
TEST=Follow the steps:
1. Use the latest test image. The issue occurred recently.
2. Install the test from chroot
(cr) cd ~/trunk/src/scripts
(cr) $ run_remote_tests.sh
--autotest_dir ~/trunk/src/third_party/autotest/files
--remote=172.30.210.179 firmware_TouchMTBSetup
3. Run the autotest on a chromebook machine.
$ cd /usr/local/autotest/tests/firmware_TouchMTB
$ DISPLAY=:0 python main.py -m complete
It should execute normally.
Change-Id: Iedc1360dc029cc2161e63c6646418429080cabf1
Reviewed-on: https://chromium-review.googlesource.com/200730
Reviewed-by: Charles Mooney <charliemooney@chromium.org>
Tested-by: Charles Mooney <charliemooney@chromium.org>
Commit-Queue: Shyh-In Hwang <josephsih@chromium.org>
/external/autotest/client/site_tests/firmware_TouchMTB/firmware_window.py
|
| f669f3062ea1192553f2305432c568ad1eb64217 |
|
02-Apr-2014 |
Joseph Hwang <josephsih@chromium.org> |
firmware_TouchMTB: close gracefully when KeyboardInterrupt is captured
When the Keyboard Interrupt is captured, call the close() method
to exit FirmwareWindow object gracefully. This also allows the
firmware_TouchMTB object in main.py to do its own cleanup gracefully.
BUG=chromium:353874
TEST=Record some gestures in a chromebook machine.
$ cd /usr/local/autotest/tests/firmware_TouchMTB
$ DISPLAY=:0 python main.py -m complete
Follow the prompts to record a few gestures, and press ctrl-c
to interrupt the tests. Observe that it shows the message:
Display the html test report on the browser.
This may take a while...
... (followed by more messages)
Change-Id: I79fbf3d563d4a9fd24aa36c2e36581597d02db96
Reviewed-on: https://chromium-review.googlesource.com/192713
Reviewed-by: Charles Mooney <charliemooney@chromium.org>
Tested-by: Shyh-In Hwang <josephsih@chromium.org>
Commit-Queue: Shyh-In Hwang <josephsih@chromium.org>
/external/autotest/client/site_tests/firmware_TouchMTB/firmware_window.py
|
| 8abd550453a67f7abb6eb2042ed4298dd10ec5b0 |
|
21-Mar-2014 |
Joseph Hwang <josephsih@chromium.org> |
firmware_TouchMTB: fix the gtk environment problems
After a tester performs a gesture, the mtplot screen is dumped
and should be displayed in the gesture capture window. However,
it failed to display the image file now due to some broken
configurations about gtk.
Specifically,
- Problem 1: The gtk library expects the GdkPixbuf image loader modules file
at "/etc/gtk-2.0/gdk-pixbuf.loaders"
which is actually at "/usr/local/etc/gtk-2.0/gdk-pixbuf.loaders"
- Problem 2: In the above GdkPixbuf image loader modules file, it
specifies the *.so image modules to be at "/usr/lib*/..."
which is actually at "/usr/local/lib*/..."
Problem 1 could be resolved by setting the environment variable
GDK_PIXBUF_MODULE_FILE to the proper path.
Problem 2 could be resolved by making a temporary symbolic link
when conducting the gesture recording process.
BUG=chromium:353874
TEST=Record some gestures in a chromebook machine.
$ cd /usr/local/autotest/tests/firmware_TouchMTB
$ DISPLAY=:0 python main.py -m complete
Follow the prompts to record a few gestures, and press 'x' to quit.
Observe that the mtplot images of the performed gestures are
displayed in the X window each time a gesture is performed.
Change-Id: I1c38b374a3d9654582b8332c58e2694862dd94e1
Reviewed-on: https://chromium-review.googlesource.com/190996
Reviewed-by: Charles Mooney <charliemooney@chromium.org>
Tested-by: Shyh-In Hwang <josephsih@chromium.org>
Commit-Queue: Shyh-In Hwang <josephsih@chromium.org>
/external/autotest/client/site_tests/firmware_TouchMTB/firmware_window.py
|
| 1fd993155b6d1c6996daafd5789101d3342c7bc9 |
|
01-Jul-2013 |
Joseph Hwang <josephsih@chromium.org> |
firmware_TouchMTB: do not upload data by default
Since our partners are running our firmware test suite now, we
should disable uploading of any data to google servers by default.
To upload the data later when needed, use the option "-u/--upload"
to specify a test result directory under
"/var/tmp/touch_firmware_test". Refer to the example below for
more details.
BUG=chromium:254992
TEST=Conduct the firmware tests on a chromebook machine.
$ cd /usr/local/autotest/tests/firmware_TouchMTB
$ DISPLAY=:0 OPTIONS="-m complete" python main.py
After all tests have been finished, observe that the data are not
uploaded. Instead, it displays the following messages.
You can upload all data in the latest result directory:
$ DISPLAY=:0 OPTIONS="-u latest" python main.py
You can also upload any test result directory, e.g.,
"20130702_063631-fw_1.23-manual", in "/var/tmp/touch_firmware_test"
$ DISPLAY=:0 OPTIONS="-u 20130702_063631-fw_11.23-manual" python main.py
Change-Id: Ibbcc272b0f9241e8026e8f5c2b9464e9d79d61cb
Reviewed-on: https://gerrit.chromium.org/gerrit/60742
Commit-Queue: Joseph Shyh-In Hwang <josephsih@chromium.org>
Tested-by: Joseph Shyh-In Hwang <josephsih@chromium.org>
Reviewed-by: Joseph Shyh-In Hwang <josephsih@chromium.org>
/external/autotest/client/site_tests/firmware_TouchMTB/firmware_window.py
|
| 8c5e275df682ef5b0ad52574ae1e2e31fc724509 |
|
22-Apr-2013 |
Joseph Hwang <josephsih@chromium.org> |
firmware_TouchMTB: Rename the test suite and fix the programs
To finish renaming the test suite, we also need to fix the prompts,
classes, methods, variables, and strings, etc. to reduce confusion.
BUG=chromium:234117
TEST=Install the test suite to a chromebook
(cr) $ ./run_remote_tests.sh --autotest_dir
~/trunk/src/third_party/autotest/files --remote=$MACHINE_IP
firmware_TouchMTB
On the chromebook, conduct the test suite as follows.
$ DISPLAY=:0 python main.py
It should execute normally.
Change-Id: Iaf5d5060bf68e3e0a13913a69227636fba2fbeb6
Reviewed-on: https://gerrit.chromium.org/gerrit/48782
Reviewed-by: Charlie Mooney <charliemooney@chromium.org>
Commit-Queue: Joseph Shyh-In Hwang <josephsih@chromium.org>
Tested-by: Joseph Shyh-In Hwang <josephsih@chromium.org>
/external/autotest/client/site_tests/firmware_TouchMTB/firmware_window.py
|
| 0cbff8bf3666a81b886080f82712943e36dad95f |
|
22-Apr-2013 |
Joseph Hwang <josephsih@chromium.org> |
firmware_TouchMTB: Rename the test suite as firmware_TouchMTB
As the test suite is now applicable to both the touchpad
and the touchscreen, it is proper to rename the test name
from firmware_TouchpadMTB to firmware_TouchMTB.
BUG=chromium:234117
TEST=None. Will be combined with next patch.
Change-Id: I92ecc074023c76f7c2f292b7e22ef960d537819f
Reviewed-on: https://gerrit.chromium.org/gerrit/48781
Reviewed-by: Charlie Mooney <charliemooney@chromium.org>
Commit-Queue: Joseph Shyh-In Hwang <josephsih@chromium.org>
Tested-by: Joseph Shyh-In Hwang <josephsih@chromium.org>
/external/autotest/client/site_tests/firmware_TouchMTB/firmware_window.py
|