| commit | ac1d147f91aba29be7f979888fef88dfe1861b8b | [log] [tgz] |
|---|---|---|
| author | Mary Ruthven <mruthven@google.com> | Thu Mar 15 14:52:41 2018 -0700 |
| committer | chrome-bot <chrome-bot@chromium.org> | Mon Mar 19 21:34:30 2018 -0700 |
| tree | b3aa65dbd18fa50718c6c7a17329bc89dfd89293 | |
| parent | 15b78cf68518521fc33a34b57c4d343f160d5842 [diff] |
cr50_stress_experimental: add firmware_Cr50RMAOpen Cr50 has RMA Open support. This change adds a test to verify different RMA features. It verifies the opening, rate limiting, and challenge generation through the AP and command line interfaces. There are two sets of keys images can be built with: test and prod. At some point prepvt flagged images will use test keys and prod flagged will use prod keys. The test cannot generate authcodes for prod keyed images, so it will verify that test authcodes will not open Cr50. If the test sees Cr50 is using test keys, it will verify that RMA open succeeds with the generated authcodes. Since the test cannot verify RMA open succeeds with prod keys, images with prod keys will need to be verified manually. This test can still be used to verify the challenge rate limiting and other basic functionality. This test will also fail if it sees a MP signed prod flagged image with test keys. BUG=none BRANCH=none TEST=run on 2.2, 1.2, and 3.3 built with test keys and one with prod keys Change-Id: Ie1aac0a6a385e1586fc468c0563eba64d20a5a79 Signed-off-by: Mary Ruthven <mruthven@google.com> Reviewed-on: https://chromium-review.googlesource.com/964864 Commit-Ready: Mary Ruthven <mruthven@chromium.org> Tested-by: Mary Ruthven <mruthven@chromium.org> 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.