| 5ca714888586b4e1976dfae98b4f26b25d0d6a32 |
|
15-Dec-2016 |
Shelley Chen <shchen@chromium.org> |
FAFT: Modifying tests to use simple_reboot method
BUG=chrome-os-partner:60721
BRANCH=None
TEST=Ran various tests on Kevin in dev and normal mode
to ensure that they still pass
Change-Id: I04b015c7f84b98df2247c6d3cf6fa834f1fb02c8
Signed-off-by: Shelley Chen <shchen@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/420484
Reviewed-by: Wai-Hong Tam <waihong@google.com>
/external/autotest/server/site_tests/firmware_SelfSignedBoot/firmware_SelfSignedBoot.py
|
| 19bfb6ea468c34e1b44842033eb784c2ef3eed42 |
|
20-Aug-2015 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Move wait_for_client and wait_for_client_offline to ModeSwitcher
These two methods are tightly related to ModeSwitcher. This change
helps it to be derived to different implementations.
BUG=chrome-os-partner:39744
TEST=Ran some of the effected FAFT tests.
Change-Id: Id9be1decec3ebc5a843a30b3070a2352546423eb
Reviewed-on: https://chromium-review.googlesource.com/294773
Commit-Ready: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
Reviewed-by: danny chan <dchan@chromium.org>
/external/autotest/server/site_tests/firmware_SelfSignedBoot/firmware_SelfSignedBoot.py
|
| 2a08e562f71e7b8d4a7b6b8ace01db92ac638c80 |
|
20-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Remove unnecessary hard-coded Ctrl-U pressing logic
Embedded devices don't have keyboard for the Ctrl-U logic. This
change removes it and uses ModeSwitcher to trigger dev_boot_usb mode.
BUG=chrome-os-partner:39744
TEST=Ran firmware_DevBootUSB and firmware_SelfSignedBoot on Whirlwind.
Change-Id: Ie547e363ccfd27f4a1ff25abdf67a99d9ac5256d
Reviewed-on: https://chromium-review.googlesource.com/272433
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_SelfSignedBoot/firmware_SelfSignedBoot.py
|
| 0430288e1ea7c2976db8612c595223dc2a220563 |
|
14-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Abstract the firmware screen bypass logic to FwBypasser class
Introduces a new FwBypasser class which abstract the firmware bypass
behaviors, like:
- bypass_dev_mode
- bypass_dev_boot_usb
- bypass_rec_mode
- trigger_dev_to_rec
- trigger_rec_to_dev
- trigger_dev_to_normal
The FwBypasser is created in ModeSwitcher and its methods are also
exposed to ModeSwitcher too.
It merges the delay of waiting dev screen into the firmware screen,
simplifies the USB replug logic, moves some not-frequently-used
methods to the tests.
BUG=chrome-os-partner:16231
TEST=Ran suites faft_lv1, faft_lv2, faft_lv3, and faft_lv4 on Samus.
Change-Id: Ie46924d1122b9ff78625ca0d562747e04a0f826d
Reviewed-on: https://chromium-review.googlesource.com/271282
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Tom Tam <waihong@google.com>
Commit-Queue: Tom Tam <waihong@google.com>
/external/autotest/server/site_tests/firmware_SelfSignedBoot/firmware_SelfSignedBoot.py
|
| eeed7fb22ebdabb9454ee6020072559532796c0d |
|
08-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Install Autotest dependency automatically
FAFT tests used to explicitly to install Autotest dependency when
booting into an USB image as it may not have Autotest there. It
makes a bit confusion if it is needed or not. This change removes
this confusion by always installing Autotest dependency when the
original connection to DUT is lost, meaning that a new RPC
connection has to be established, furthermore better to ensure
Autotest dependency is also there.
BUG=chrome-os-partner:16231
TEST=Removed the Autotest directory from the USB stick, ran
firmware_RecoveryButton test, and checked Autotest reinstalled.
Change-Id: I6cfc4f0bf3fb6b5386115a9464bb042059849bb5
Reviewed-on: https://chromium-review.googlesource.com/270101
Trybot-Ready: Tom Tam <waihong@google.com>
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_SelfSignedBoot/firmware_SelfSignedBoot.py
|
| eabe8051fc4b0112529d9e93bd35e5d951a452b8 |
|
07-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Simplify test flows by using wait_for_dut_up=True
It modifies test flows to reuse the mode_aware_reboot method to
wait for DUT up, not to do duplicated works.
BUG=chrome-os-partner:16231
TEST=Ran all affected FAFT tests on Jerry.
Change-Id: I55ec5b5b6dd8181a8ba56838ad6cecfe544a111b
Reviewed-on: https://chromium-review.googlesource.com/270014
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_SelfSignedBoot/firmware_SelfSignedBoot.py
|
| 4777624b69b3b223a5d3c3abe86000783f6c0e96 |
|
06-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Use mode_aware_reboot instead of reboot_warm and reboot_cold
This change removes reboot_warm, reboot_cold, reboot_warm_trigger,
and reboot_cold_trigger from FAFT framework and uses the new
mode_award_reboot method which does the same job.
BUG=chrome-os-partner:16231
TEST=Ran some of the affected FAFT tests on Jerry.
Change-Id: I9f0d1fd3416c7e4a624a915507dfa9c97f16d3e0
Reviewed-on: https://chromium-review.googlesource.com/269764
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_SelfSignedBoot/firmware_SelfSignedBoot.py
|
| 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_SelfSignedBoot/firmware_SelfSignedBoot.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_SelfSignedBoot/firmware_SelfSignedBoot.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_SelfSignedBoot/firmware_SelfSignedBoot.py
|
| 408c995796074681102313315b4ee6726a6b5392 |
|
29-Apr-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Remove Ctrl-U logic and eliminate press_key methods from FAFT framework
Once servo supports simluating all the key combinations in
https://chromium-review.googlesource.com/#/c/267813/
, the special Ctrl-U logic is no longer needed. As a result, the
press_key methods in FAFT framework layer can be eliminated.
Tests now call the servo key simlution methods directly, like other
non-FAFT tests.
BUG=chrome-os-partner:39653
CQ-DEPEND=CL:267813
TEST=Deploy the above change to servod. Run the affected tests, e.g.
firmware_DevMode,
firmware_DevBootUSB,
firmware_DevScreenTimeout,
firmware_SelfSignedBoot, and
firmware_SoftwareSync.
Change-Id: Ib0af6ac85a518cc508ab33cb072f816c057a6cc2
Reviewed-on: https://chromium-review.googlesource.com/268312
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_SelfSignedBoot/firmware_SelfSignedBoot.py
|
| 095e26f809f4dd17e1010cc20c2a9e7e1c1076cf |
|
09-Jul-2014 |
Yusuf Mohsinally <mohsinally@google.com> |
Install dependencies in additional steps firmware_SelfSignedBoot.
There were some places that autotest dependencies were not installed after
reboots. This is now resulting in BadStatusLine exceptions because the files
are missing when trying to start the RPCserver.
This seems to have started happening because of the way the new powerhandling
code implements the rec mode and reboot procedure.
BUG=None
TEST=Manual runs against wolf device
Change-Id: I9d338cd8f71099f71a418034f63ec9508fad91ab
Reviewed-on: https://chromium-review.googlesource.com/207066
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_SelfSignedBoot/firmware_SelfSignedBoot.py
|
| a5a74c0204b8d652d744385d2aa1165833119123 |
|
19-May-2014 |
Yusuf Mohsinally <mohsinally@google.com> |
Converting firmware_SelfSignedBoot 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: Ib5055e298629b572ffb27cb7cf595d93de4edb32
Reviewed-on: https://chromium-review.googlesource.com/200404
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_SelfSignedBoot/firmware_SelfSignedBoot.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_SelfSignedBoot/firmware_SelfSignedBoot.py
|
| 1d58c53d984e3dc0fe22f48c70edbed1c2ecbb44 |
|
27-Aug-2013 |
Tom Wai-Hong Tam <waihong@chromium.org> |
FAFT: Use better naming for FAFTConfig and get_usbdisk_path_on_dut
The Config imported from faft config is renamed to FAFTConfig.
And the method get_dut_usb_dev is renamed to get_usbdisk_path_on_dut.
BUG=None
TEST=Manual
Ran firmware_SelfSignedBoot test on Spring and passed.
Change-Id: Icb528bec584a8fa813d98e5fe661913a44f90391
Reviewed-on: https://chromium-review.googlesource.com/67047
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Wai-Hong Tam <waihong@chromium.org>
Tested-by: Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_SelfSignedBoot/firmware_SelfSignedBoot.py
|
| a39f97038dfa865c7bfcea2625d516d098207066 |
|
16-Aug-2013 |
Yusuf Mohsinally <mohsinally@google.com> |
Refactoring config settings for devices in FAFT tests.
Created a new config system for faft tests which allow for a default file of
settings and override file for each board that requires it.
The default and override files contain a class called 'Values', in which
the config attributes are stored. The class allows for inheritence of config
values from to better organize related board settings.
The new config system provides for one 'Config' class which is the main
interface to settings for all tests. It does a cascading search, for the
requested attribute, first checking a platform specific overrides, and then
through the defaults.
Modified FAFTSequence to contain one attribute 'faft_config' which replaces
self.client_attr and self.delay which it made available to tests.
BUG=None
TEST=Manual runs of various tests at desk on link device
Change-Id: I06da7be07364d5d99bdf6b204d628ad849f8d617
Reviewed-on: https://gerrit.chromium.org/gerrit/66006
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Yusuf Mohsinally <mohsinally@google.com>
/external/autotest/server/site_tests/firmware_SelfSignedBoot/firmware_SelfSignedBoot.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_SelfSignedBoot/firmware_SelfSignedBoot.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_SelfSignedBoot/firmware_SelfSignedBoot.py
|
| 96864aec339b476ddaa23831a68548caea43e351 |
|
31-Jul-2013 |
Shawn Nematbakhsh <shawnn@chromium.org> |
firmware_SelfSignedBoot: Add servo USB media auto-detect on dut.
Previously, servo USB device was hard-coded based upon CPU architecture.
Change the test to do autodetection.
BUG=chrome-os-partner:21171.
TEST=Run firmware_SelfSignedBoot on peppy, verify pass.
Change-Id: Iad8735bccf5f9a36c7c86a3fa2c9bf3136f5e03d
Reviewed-on: https://gerrit.chromium.org/gerrit/63790
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: Shawn Nematbakhsh <shawnn@chromium.org>
Tested-by: Shawn Nematbakhsh <shawnn@chromium.org>
/external/autotest/server/site_tests/firmware_SelfSignedBoot/firmware_SelfSignedBoot.py
|
| ed68e585da0901456f9222976490a3ff94ea428b |
|
15-May-2013 |
Vic Yang <victoryang@chromium.org> |
Raise TestNAError for tests requiring not supported EC functions
TestNAError is more descriptive and suitable in this case. Let's raise
it instead of current TestError.
BUG=None
TEST=Run firmware_FwScreenLidClose on Spring and see TestNA.
Change-Id: Id8c21792a6a159ebb57f9805adec277141f81d40
Signed-off-by: Vic Yang <victoryang@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/51297
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
/external/autotest/server/site_tests/firmware_SelfSignedBoot/firmware_SelfSignedBoot.py
|
| 3cbb9cbe2f63449e3b722856a7ed9e07bf93457e |
|
28-Feb-2013 |
Ismail Noorbasha <ismail@chromium.org> |
Servo based developer mode boot only test to Self signed Kernels.
Enabling dev_boot_signed_only=1 and dev_boot_usb=1 and, pressing Ctrl-U on
developer screen should not boot to the USB disk(having recovery keys).
On resigning usb image with SSD keys pressing Ctrl-U should boot the USB disk.
More details: Refer to chrome-os-partner issue 5954(#37).
BUG=None
TEST=./run_remote_tests.sh --remote=<ip> --servo --board=<> firmware_SelfSignedBoot
Change-Id: I8f859b459104d5eb54bc2355d907693c19df8206
Reviewed-on: https://gerrit.chromium.org/gerrit/44338
Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org>
Commit-Queue: Ismail Noorbasha <ismail@chromium.org>
Tested-by: Ismail Noorbasha <ismail@chromium.org>
/external/autotest/server/site_tests/firmware_SelfSignedBoot/firmware_SelfSignedBoot.py
|