| commit | b537c7962b37dade403177b2fae6da76dcc845b8 | [log] [tgz] |
|---|---|---|
| author | Benjamin Gordon <bmgordon@chromium.org> | Thu May 09 11:10:58 2019 -0600 |
| committer | chrome-bot <chrome-bot@chromium.org> | Sun May 12 19:27:46 2019 -0700 |
| tree | 2989f461824bd189d47eb5bacafad81879e30d07 | |
| parent | fbf71da0a06021350eaa323e0ce592718101a41c [diff] |
arc.py: Ignore apk install failures in arc_setup Some tests attempt to install an apk of the correct arch by installing several apks and assuming the incorrect ones will silently fail. These tests previously worked because at least one arch would successfully install. With the newer adb, the install command fails instead of merely printing an error. Change arc_setup to ignore install failures so that this use case works like before. The test should still be useful because it verifies that it can find an installed package with the expected name after trying all apks. BUG=b:130585881 TEST=cheets_MailBench, cheets_ScreenRotation make it past apk installs Change-Id: I446973abaafb660ed9304c98021aee24d904c56a Reviewed-on: https://chromium-review.googlesource.com/1602670 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Benjamin Gordon <bmgordon@chromium.org> Reviewed-by: Shao-Chuan Lee <shaochuan@chromium.org>
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.