| commit | a856535503bb3c578c9bafc5e2646099037d9a96 | [log] [tgz] |
|---|---|---|
| author | Aseda Aboagye <aaboagye@google.com> | Wed May 25 18:20:52 2016 -0700 |
| committer | chrome-bot <chrome-bot@chromium.org> | Thu May 26 14:34:27 2016 -0700 |
| tree | c1a6ebc0748d485620859c63468c95fc64cdb311 | |
| parent | c92a3361eb4aa9f3b61df66033fcbee5cbf90bee [diff] |
firmware_ECKeyboardReboot: Increase wait_up time. Currently, firmware_ECKeyboardReboot has been very flaky. In some of my own experiments, I've found the issue to be that the 30 seconds that we wait for the DUT to come up is _very_ close to the time it takes for a device to reboot and establish a link using the USB ethernet adapter. The test often fails with the error that 'DUT is off, expected on', when the DUT actually *is* on. This test should really be testing whether a DUT comes up or not and not "how quickly". Therefore, increase the time to wait for the DUT to come up to 60 seconds. This won't be sufficient for a network outage, but it at least should provide a bit more room for random delays in the network. No harm is done if the DUT comes up earlier. BUG=None BRANCH=None TEST=Run firmware_ECKeyboardReboot on a cyan and observe failures. Apply this patch and repeat the tests and observe no failures. Change-Id: I3448d89ceab3dda57efcca096d6f97513eca6aa5 Signed-off-by: Aseda Aboagye <aaboagye@google.com> Reviewed-on: https://chromium-review.googlesource.com/347490 Commit-Ready: Aseda Aboagye <aaboagye@chromium.org> Tested-by: Aseda Aboagye <aaboagye@chromium.org> Reviewed-by: Tom 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.