| commit | 37d15312982290257ef1ef3aa47ebe0f3a1c43d2 | [log] [tgz] |
|---|---|---|
| author | Lenine Ajagappane <leninex.ajagappane@intel.com> | Wed Jan 24 16:27:04 2018 +0530 |
| committer | chrome-bot <chrome-bot@chromium.org> | Thu Jan 25 00:15:49 2018 -0800 |
| tree | a7878b83966a2a46cc10b5f05545e098c3f6defd | |
| parent | d46cacdcb3367be62d1e1fb72b6390d660cea48a [diff] |
FAFT: Adding check to confirm the switched mode after setup_mode & restore_mode When test calls setup_mode or restore_mode, mode_switcher switches the DUT to requested mode and then continues the test. But the mode_switcher not confirming whether the system is really switched to requested mode or not. This will impact the tests when the DUT firmware having issues with mode switching. (i.e.,) For example in CPFE-10144 FW, mode switching from Normal to Developer mode is broken by default. But this was not found by the mode_switcher after performing setup_mode or restore_mode and test continues to execute & passed at the end. (e.g. firmware_ECWriteProtect.dev, firmware_TPMVersionCheck.dev). BUG=None Branch=None TEST= Verified all the FAFT tests with CPFE-10144 FW & working FW on Soraka board. Change-Id: I59633f823133daaabd2f92fdbceed16d81465f08 Signed-off-by: Lenine Ajagappane <leninex.ajagappane@intel.com> Reviewed-on: https://chromium-review.googlesource.com/883301 Commit-Ready: Naresh Solanki <naresh.solanki@intel.corp-partner.google.com> Tested-by: Naresh Solanki <naresh.solanki@intel.corp-partner.google.com> Reviewed-by: Naresh Solanki <naresh.solanki@intel.com> Reviewed-by: Wai-Hong Tam <waihong@google.com>
Autotest is a framework for fully automated testing. It was originally designed to test the Linux kernel, and expanded by the Chrome OS team to validate complete system images of Chrome OS and Android.
Autotest is composed of a number of modules that will help you to do stand alone tests or setup a fully automated test grid, depending on what you are up to. A non extensive list of functionality is:
A body of code to run tests on the device under test. In this setup, test logic executes on the machine being tested, and results are written to files for later collection from a development machine or lab infrastructure.
A body of code to run tests against a remote device under test. In this setup, test logic executes on a development machine or piece of lab infrastructure, and the device under test is controlled remotely via SSH/adb/some combination of the above.
Developer tools to execute one or more tests. test_that for Chrome OS and test_droid for Android allow developers to run tests against a device connected to their development machine on their desk. These tools are written so that the same test logic that runs in the lab will run at their desk, reducing the number of configurations under which tests are run.
Lab infrastructure to automate the running of tests. This infrastructure is capable of managing and running tests against thousands of devices in various lab environments. This includes code for both synchronous and asynchronous scheduling of tests. Tests are run against this hardware daily to validate every build of Chrome OS.
Infrastructure to set up miniature replicas of a full lab. A full lab does entail a certain amount of administrative work which isn't appropriate for a work group interested in automated tests against a small set of devices. Since this scale is common during device bringup, a special setup, called Moblab, allows a natural progressing from desk -> mini lab -> full lab.
See the guides to test_that and test_droid:
See the best practices guide, existing tests, and comments in the code.
git clone https://chromium.googlesource.com/chromiumos/third_party/autotest
See the coding style guide for guidance on submitting patches.
You need to run utils/build_externals.py to set up the dependencies for pre-upload hook tests.