| da6c6ba556ebb2b810dd7450860609d6725afb1d |
|
01-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Support waiting DUT online after mode switching
A new argument wait_for_dut_up added to reboot_to_mode method. If
wait_for_dut_up=True, wait DUT online again. If wait_for_dut_up=False,
do the reboot and mode switching sequence only and may need more
operations to pass the firmware screen.
Also change most of the tests to use the default wait_for_dut_up=True
way, it helps porting these tests to different mode switching
implementations, like using dev and rec buttons.
BUG=chrome-os-partner:39744
TEST=Ran the affected test cases, like firmware_DevMode,
firmware_RecoveryButton, firmware_SelfSignedBoot, etc.
Change-Id: I723d43efe65e731d8a26b94822c094a9de8e8f11
Reviewed-on: https://chromium-review.googlesource.com/268859
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
Tested-by: Tom Tam <waihong@google.com>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| 0cc9a4fe28f221cfc73bb35c30fa79338c4b43f1 |
|
01-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Refactor setup_mode and restore_mode
The change moves and splits the original logic on setup_dev_mode and
restore_dev_mode to FAFTCheckers and ModeSwitcher. It is also enhanced
to support setting up all firmware modes, including recovery. They are
now methods in ModeSwitcher as they are highly related to mode
switching.
BUG=chrome-os-partner:39744
TEST=Switched DUT to normal mode and ran firmware_DevMode. Then
switched DUT to dev mode and run firmware_DevMode. Checked DUT
restored to the original mode state.
Change-Id: I16314d18b785da59473df3ef5e02f7fe8f2693b0
Reviewed-on: https://chromium-review.googlesource.com/268858
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
Tested-by: Tom Tam <waihong@google.com>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| f2de4debd08a4825542fd4fd848ccd6b4fb000f8 |
|
01-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Implement the ModeSwitcher class
This is the first change of the ModeSwitcher refactoring. It
introduces a new class ModeSwitcher to do normal, dev, and rec
mode switching sequence. The triggering logic mostly keeps the
same or does a minor modification from the original one.
BUG=chrome-os-partner:39744
TEST=Ran firmware_DevMode and firmware_RecoveryButton on Jerry.
These two tests cover major changes on switching to normal, dev,
and rec modes.
Change-Id: I96b435c6df7a9f4c80aaab5d1fa4a062aa7699bf
Reviewed-on: https://chromium-review.googlesource.com/268794
Tested-by: Tom Tam <waihong@google.com>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| 74d98c72d49568d84c03b6aa60d910733b7ce46a |
|
19-May-2014 |
Yusuf Mohsinally <mohsinally@google.com> |
Converting firmware_DevMode to use new FirmwareTest class.
The new FirmwareTest class does not require the traditional dict of objects
that FAFTSequence required.
1. Converted the test to use the new flat function call style.
BUG=chromium:371185
TEST=Manually ran this test at desk against peppy device.
Change-Id: I2bd30240a4bfc30fb5dce72de560261487b58b20
Reviewed-on: https://chromium-review.googlesource.com/200396
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| 1f115ae9ee3c043e9577e7ce9872dc99323fdcb3 |
|
07-Nov-2013 |
Yusuf Mohsinally <mohsinally@chromium.org> |
Correctly using initialize() rather than setup() for FAFT tests.
FAFT tests have been using setup() (which is run once at autotest init), when
it should have instead used initialize() for running code before each
test case is run.
BUG=chromium:267175
TEST=Ran tests manually against Pit device to ensure that these changes did not
introduce problems.
Change-Id: If0e76e12b9f40249154d7b95a1375b2787a56304
Reviewed-on: https://chromium-review.googlesource.com/176024
Reviewed-by: Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| 73c28f3abd6ec8de4dc5a8e6afca1d5e83eb59c7 |
|
03-Aug-2013 |
Yusuf Mohsinally <mohsinally@google.com> |
Reorginazing FAFT (server side) files.
Initial reorganization step while moves FAFT (autotest/server)
files over to packages. Naming and other cleanup will be performed
in additional CLs.
BUG=None
TEST=built and ran faft tests at desk against Link
Change-Id: I83712620c0e6816ec08b9afdf8c227a800734ea6
Reviewed-on: https://gerrit.chromium.org/gerrit/64408
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Yusuf Mohsinally <mohsinally@chromium.org>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| d4340315f76fcae9a5e9430d0446705f4f8fa7b7 |
|
17-Jul-2013 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Rename the module faftsequence to faft_classes
For preparing the future refactoring that splitting FAFTSequence into
multiple meaningful small classes, changes the original module name
faftsequence to faft_classes.
BUG=chrome-os-partner:21118
TEST=Manual
Ran the affected test cases, firmware_FAFTSetup, on Spring and passed.
Change-Id: I662cfc8d37a54711d7c52ff5322ed28a9a759ffe
Reviewed-on: https://gerrit.chromium.org/gerrit/62642
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| 56977787b3cca08fbf5d76bf5d390c3305929547 |
|
23-Nov-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Speed up the waiting time for dev screen and sync
Waiting for a dev screen and pressing Ctrl-D is a recurrent action.
Booting to a dev screen is a bit faster than other firmware screens,
like recovery insert screen. We can make the dev screen a separated
case from other firmware screens for speed-up. It can save 3 seconds
each time.
Also the sync delay can be faster, from 5 seconds to 2 seconds.
BUG=chromium-os:34392
TEST=run FAFT suite on Link and the dev screen timing is correct.
Change-Id: I377494cc44b4bb9ca3e2d2addee3cb34a2d511d0
Reviewed-on: https://gerrit.chromium.org/gerrit/38630
Reviewed-by: Vic Yang <victoryang@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| 700c9fd170eab25bcd60e56ac9b5f3c40b87d6f1 |
|
15-Nov-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Support tests running in EC WP'ed and add a new test suite for them
In order to check EC WP behavior, we enables EC WP at the beginning of tests,
runs the same tests on normal mode, and restores the original EC WP state.
This new test suite (suite:faft_ec_wp) now contains all faft_lv1 and faft_lv2
test cases.
BUG=chrome-os-partner:15835
TEST=run_remote_tests --board link --remote dut suite:faft_ec_wp
Change-Id: I91096d463ce8ad0503e021b5d81b53a3d95116dc
Reviewed-on: https://gerrit.chromium.org/gerrit/38114
Reviewed-by: Vic Yang <victoryang@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| b09a04183cf7017eb4b30ad28f5f81f1204c36b3 |
|
06-Nov-2012 |
Vic Yang <victoryang@chromium.org> |
faft: Fix lint warning and error
This includes removing unnecessary 'pass' and unused argumenets.
BUG=chrome-os-partner:35902
TEST=Check tests still work.
Change-Id: Ifb9ac8348e7e26e2ea1a10b9c7e509f817e117b9
Signed-off-by: Vic Yang <victoryang@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/37424
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| ebf4094ae637680bfcfbf4d43a36e9dd7b1a4e54 |
|
05-Nov-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Ensure DevMode and TryFwB tests going back to their original modes
The DevMode and TryFwB tests may not go back to their original modes
on test failures, like DevMode may end with a different mode, TryFwB
may end with firmware B booting. This CL is to add a check to ensure
these tests going back.
BUG=chromium-os:35902
TEST=run_remote_tests.sh --board link --remote dut DevMode TryFwB/control$
Change-Id: If312fdc53a5210e29c42042e56d18a78df2ffd68
Reviewed-on: https://gerrit.chromium.org/gerrit/37334
Reviewed-by: Vic Yang <victoryang@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| 893bcc0871678b7ba9f70ac1f189e19db8c8db18 |
|
02-Nov-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Unify all USB disk setup code in a new method setup_usbkey()
This CL adds a new method setup_usbkey() in FAFTSequence class, which
helps all USB disk related setup and check. Its usage:
If the test requires USB key (Chrome OS test image inside) and muxes to host:
self.setup_usbkey(usbkey=True, host=True)
If the test requires USB key (Chrome OS test image inside) and muxes to DUT:
self.setup_usbkey(usbkey=True, host=False)
If the test does not requires USB key:
self.setup_usbkey(usbkey=False)
BUG=chromium-os:35902
TEST=run the FAFT suite:
$ run_remote_tests.sh --board link --remote dut suite:faft_bios
Change-Id: If6eb94ee52f612df568c4f2f07a7acbbdd0a0b66
Reviewed-on: https://gerrit.chromium.org/gerrit/37193
Reviewed-by: Vic Yang <victoryang@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| f93f702b4e2b59bab22cde8d4d05b35a31520f6a |
|
31-Oct-2012 |
Vic Yang <victoryang@chromium.org> |
faft: Move FAFT checkers to a separate module
BUG=chrome-os-partner:35902
TEST=Run FAFT suites and check they still work fine.
Change-Id: Idfb60632b67e7bc92b4ae12a60269e00c7b90b77
Signed-off-by: Vic Yang <victoryang@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/36989
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| 0b9e6d72d1b8d3838df1fe29e1171281e73fc651 |
|
31-Jul-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Better names for methods like enable_dev_mode_and_reboot
Since there is no dev and normal firmware anymore. Now switching to dev/normal
mode needs reboot flow. So change better names for the methods.
BUG=chrome-os-partner:11694
TEST=Run firmware_DevMode on Snow passed.
Change-Id: I67acf267a492fae707554dd4d2fb4cf67e0ca199
Reviewed-on: https://gerrit.chromium.org/gerrit/28900
Reviewed-by: Vic Yang <victoryang@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| e03c32a4277b19cd0e5b0d68eaa5e44f0308daba |
|
26-Jul-2012 |
Tom Wai-Hong Tam <waihong@chromium.org> |
faft: Remove the Alex/ZGB legacy dev transition state in DevMode test
The dev transition state is deprecated and only used in Alex/ZGB firmware.
This CL removes that checks and simplify the DevMode test. It uses the new
dev/normal switching methods which support keyboard controlled dev mode.
BUG=chrome-os-partner:9223
TEST=run firmware_DevMode on Link passed.
Change-Id: I9d2eaf4e2d57945e186d5dc2c6b7266ba75f82da
Reviewed-on: https://gerrit.chromium.org/gerrit/28481
Reviewed-by: Vic Yang <victoryang@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| 678ab15e469e25c1c821dde6e3af87a3d4c324fa |
|
14-Dec-2011 |
Tom Wai-Hong Tam <waihong@chromium.org> |
Get the platform name using mosys instead of the firmware ID.
Using mosys is more reliable than the firmware ID. A typo is also fixed.
BUG=chromium-os:19710
TEST=tested on Alex/ZGB and non-Alex/ZGB devices
$ run_remote_tests.sh --remote=$REMOTE_IP -a "xml_config=$OVERLAY_XML \
servo_vid=0x18d1 servo_pid=0x5001" DevMode/control
$ run_remote_tests.sh --remote=$REMOTE_IP -a "xml_config=$OVERLAY_XML \
servo_vid=0x18d1 servo_pid=0x5001" DevTriggerRecovery/control
$ run_remote_tests.sh --remote=$REMOTE_IP -a "xml_config=$OVERLAY_XML \
servo_vid=0x18d1 servo_pid=0x5001" CorruptBothKernelAB/control.normal
$ run_remote_tests.sh --remote=$REMOTE_IP -a "xml_config=$OVERLAY_XML \
servo_vid=0x18d1 servo_pid=0x5001" DevFwNormalBoot/control
Change-Id: Ic42c7666e70691956dee122894bd5080bc96219a
Reviewed-on: https://gerrit.chromium.org/gerrit/12897
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| 4d3fff99056f82ae5515392e1f3e65d5163a9115 |
|
24-Nov-2011 |
Tom Wai-Hong Tam <waihong@chromium.org> |
Add fwb_tries=1 steps on firmware DevMode tests.
Adding these steps increase the test coverage:
- devsw=On, fwb_tries=1, fwA=Normal, fwB=Normal => fwB boot
- devsw=Off, fwb_tries=1, fwA=Dev, fwB=Normal => fwB boot
BUG=chromium-os:19710
TEST=run_remote_tests.sh --remote=$REMOTE_IP -a "xml_config=$OVERLAY_XML \
servo_vid=0x18d1 servo_pid=0x5001" firmware_DevMode
Change-Id: I1fcbf0d299204210f4b2abaa0839346d33f6b0db
Reviewed-on: https://gerrit.chromium.org/gerrit/12112
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| a9c1a50d1f5acaca1d7410dd9d07455531d4ac34 |
|
09-Nov-2011 |
Tom Wai-Hong Tam <waihong@chromium.org> |
Disable dev mode by default and some refactoring.
Refactoring includes:
- Add setup_dev_mode() to ensure the system in the normal/dev mode.
- Move wait_fw_screen_and_ctrl_d() to FAFTSequence base class.
- Move delay timing to FAFTSequence base class.
- Increase the USB unplug and plug delay in order to see the INSERT screen.
BUG=chromium-os:22712
TEST=manaul run on Kaen
$ run_remote_tests.sh --remote=$REMOTE_IP -a \
"xml_config=servo_tegra2_kaen_overlay.xml \
servo_vid=0x18d1 servo_pid=0x5001" firmware_DevMode
$ run_remote_tests.sh --remote=$REMOTE_IP -a \
"xml_config=servo_tegra2_kaen_overlay.xml \
servo_vid=0x18d1 servo_pid=0x5001" firmware_DevTriggerRecovery
$ run_remote_tests.sh --remote=$REMOTE_IP -a \
"xml_config=servo_tegra2_kaen_overlay.xml \
servo_vid=0x18d1 servo_pid=0x5001" firmware_RecoveryButton
Change-Id: I7e2c0d91bb315a41863a68f35b15b6e2d65f2eba
Reviewed-on: https://gerrit.chromium.org/gerrit/11430
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| 8c25dd86b71104ba8987d696baecf41841d82859 |
|
09-Nov-2011 |
Tom Wai-Hong Tam <waihong@chromium.org> |
Force to reboot when running todev and tonormal firmware updater.
Since the behaviors of todev/tonormal are different between Alex/ZGB and others:
- In Alex/ZGB, todev/tonormal will reboot the system automatically.
- In other devices, todev/tonormal will not reboot.
In order to make them consistent, force to reboot after todev/tonormal finished.
BUG=chromium-os:22712
TEST=manual run on Kaen
$ run_remote_tests.sh --remote=$REMOTE_IP -a \
"servo_vid=0x18d1 servo_pid=0x5001" firmware_DevMode
$ run_remote_tests.sh --remote=$REMOTE_IP -a \
"servo_vid=0x18d1 servo_pid=0x5001" firmware_DevTriggerRecovery
Change-Id: I2d5f0201b5fffe27eeb426f8931a50a29d70aee1
Reviewed-on: https://gerrit.chromium.org/gerrit/11401
Reviewed-by: Rajesh Chenna <rchenna@chromium.org>
Tested-by: Rajesh Chenna <rchenna@chromium.org>
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| e0550de479199ef836845efa97afb3556d679158 |
|
02-Nov-2011 |
Tom Wai-Hong Tam <waihong@chromium.org> |
Rename function name from confirm_normal_boot to ensure_normal_boot.
Since these functions are not just confirming it. They are taking actions
to ensure it.
BUG=chromium-os:19710
TEST=run_remote_tests.sh --remote=$REMOTE_IP -a \
"servo_vid=0x18d1 servo_pid=0x5001" firmware_TryFwB
run_remote_tests.sh --remote=$REMOTE_IP -a \
"servo_vid=0x18d1 servo_pid=0x5001" firmware_DevMode
run_remote_tests.sh --remote=$REMOTE_IP -a \
"servo_vid=0x18d1 servo_pid=0x5001" firmware_CorruptFwA
run_remote_tests.sh --remote=$REMOTE_IP -a \
"servo_vid=0x18d1 servo_pid=0x5001" firmware_CorruptFwB
run_remote_tests.sh --remote=$REMOTE_IP -a \
"servo_vid=0x18d1 servo_pid=0x5001" firmware_UserRequestRecovery
run_remote_tests.sh --remote=$REMOTE_IP -a \
"servo_vid=0x18d1 servo_pid=0x5001" firmware_RecoveryButton
Change-Id: Ic1c38ac0fd860120c216114eb77d49b3245f5efa
Reviewed-on: https://gerrit.chromium.org/gerrit/11038
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|
| 5b4cf3130571d4037e7c361ee8514461abbd2f8f |
|
02-Sep-2011 |
Tom Wai-Hong Tam <waihong@chromium.org> |
Implement a test case for firmware developer mode boot.
It handles both Alex/ZGB and others. Since the behavior of these two kinds of
deverloper mode is different. For more details, see the comments in the code.
BUG=chromium-os:19710
TEST=run_remote_tests.sh --remote=$REMOTE_IP -a \
"servo_vid=0x18d1 servo_pid=0x5001" firmware_DevMode
Change-Id: Ife14a2911cabf9b2711c41e8e2e1a58f7fb71c1e
Reviewed-on: http://gerrit.chromium.org/gerrit/7159
Commit-Ready: Tom Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_DevMode/firmware_DevMode.py
|