| commit | 93311830627ccefc1dd2ac0a4a1d5a79881d0772 | [log] [tgz] |
|---|---|---|
| author | Caveh Jalali <[email protected]> | Fri Sep 15 22:57:56 2017 -0700 |
| committer | chrome-bot <[email protected]> | Thu Sep 28 23:26:32 2017 -0700 |
| tree | 537932b0049b45e885e9f7771b85d62466d998a2 | |
| parent | c61365458055546f7793d34202fd3f4e36fb687c [diff] |
TCPC: add FAFT test to check FW version this adds a "CompareChipFwToShellBall" test to FAFT. it probulates the DUT and cross-checks the found TCPC firmware with the firmware blobs in the system image shellball. if the system image shellball does not contain a relevant TCPC firmware blob, the test passes for that chip. the test only fails if there is a "newer" firmware blob available. Signed-off-by: Caveh Jalali <[email protected]> TEST=ran FAFT manually on an electro with: test_that --autotest_dir /home/caveh/trunk/src/third_party/autotest/files/ --board=reef 169.254.0.20 'f:.*firmware_CompareChipFwToShellBall/control' --args bios=/build/reef/firmware/image.serial.bin BUG=b:35585700 Change-Id: Iede68f4bdd832d208614ad7e5ec07c81608fb065 Reviewed-on: https://chromium-review.googlesource.com/670103 Commit-Ready: Caveh Jalali <[email protected]> Tested-by: Caveh Jalali <[email protected]> Reviewed-by: Wai-Hong Tam <[email protected]>
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.