| 2ae4244b71f60e808107434f944a120719e1e438 |
|
20-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Deprecate FAFT config keyboard_dev
The new config mode_switcher_type replaces it. Change all tests to
use mode_switcher_type instead.
BUG=chrome-os-partner:39744
TEST=Ran firmware_DevTriggerRecovery on Samus and Whirlwind.
Change-Id: I14d563e4e87307be858ba661ac0046435983f91d
Reviewed-on: https://chromium-review.googlesource.com/272434
Tested-by: Tom Tam <waihong@google.com>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: Tom Tam <waihong@google.com>
/external/autotest/server/cros/faft/config/alex.py
|
| ed4d67be4d0faa1a267d33e86905df1153d78333 |
|
19-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Create ModeSwitcher and FwBypasser according to FAFT config
Two new FAFT configs are added:
- mode_switcher_type: either 'physical_button_switcher' or
'keyboard_dev_switcher',
- fw_bypasser_type: so far only 'ctrl_d_bypasser'
FAFT checks these configs to create proper ModeSwitcher and FwBypasser.
BUG=chrome-os-partner:39744
TEST=Ran suites faft_lv1 and faft_lv2 on Samus.
Change-Id: I6a93dc6729aec571e4fc5a0e0a4468eadcbfa771
Reviewed-on: https://chromium-review.googlesource.com/272304
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Tested-by: Tom Tam <waihong@google.com>
Commit-Queue: Tom Tam <waihong@google.com>
/external/autotest/server/cros/faft/config/alex.py
|
| 3dea40e52bc58e7b19b890e2e17b3a4816227c1f |
|
13-May-2015 |
Tom Wai-Hong Tam <waihong@google.com> |
faft: Simplify Alex/ZGB flow which needs a transition state to enter dev mode
Treats this special case in a new FAFT config: need_dev_transition.
BUG=chrome-os-partner:16231
TEST=None, new devices don't use this logic.
Change-Id: Iff9dbe644f09dd3fe5bf6c2e05d2a2c513db3e82
Reviewed-on: https://chromium-review.googlesource.com/271281
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/cros/faft/config/alex.py
|
| 9ece2c6fb01d4c29d23a7238def15bdf656c885c |
|
12-Dec-2014 |
Julius Werner <jwerner@chromium.org> |
Add firmware_EventLog test to verify event log generation and timestamps
This patch adds a new faft_lv4 test to validate the functionality of the
firmware event log. It will boot the system in normal, developer and
recovery mode, verifying that the right events are logged for each. It
also tests a suspend/resume cycle, allowing either the ACPI events used
on x86 boards or the userspace Sleep/Wake events introduced with Spring
and Pit. (We can't check for 'FW Wake' because not all not-x86 boards
have a resume component in firmware.) The events are correlated to the
test section they were generated in by their timestamps, so this also
confirms that accurate timestamps are generated.
CQ-DEPEND=CL:238467
BUG=chrome-os-partner:34108
TEST=Tested on Falco (ToT), Blaze (ToT) and Pi (release). Pi failed in
the expected manner because U-Boot is missing RTC support (and all
timestamps are added as 2000-00-00). Blaze failed because its
timestamps' months are off by one... turns out the RTC driver code was
incorrectly copied from the 0-based-month-using kernel to our
1-based-month-using coreboot.
Change-Id: I2760080030468ed71dd0b7359ac69a269f6ab47a
Signed-off-by: Julius Werner <jwerner@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/238078
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
/external/autotest/server/cros/faft/config/alex.py
|
| 5d1522e5231065d4372b2a6c5d752143a5074e9e |
|
10-Jul-2014 |
Danny Chan <dchan@google.com> |
File cleanup for presubmit hook.
-Add missing docstring.
BUG=chromium:389247
TEST=None
Change-Id: I844fb2845dfb48f4d9b3d082a4f221319d992d05
Reviewed-on: https://chromium-review.googlesource.com/207246
Reviewed-by: danny chan <dchan@chromium.org>
Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
Commit-Queue: danny chan <dchan@chromium.org>
Tested-by: danny chan <dchan@chromium.org>
/external/autotest/server/cros/faft/config/alex.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/cros/faft/config/alex.py
|