commit | 078a3d00f3d112b8c21abd9136028e5a3ffe0dbb | [log] [tgz] |
---|---|---|
author | Richard Barnette <jrbarnette@chromium.org> | Fri Aug 03 14:36:54 2018 +0000 |
committer | Richard Barnette <jrbarnette@google.com> | Fri Aug 03 14:38:35 2018 +0000 |
tree | 09770c22dab3dc3670a4c6bd4e4c94f0a8488d95 | |
parent | ee032e14c32c1537215a1c00b6b943149512d15a [diff] |
Revert "Reland "[autotest] Delete Android from stable version RPC."" This reverts commit 561c2f5049974f5a2cc0048e8283efb2f1d734a2. Reason for revert: Clients in SSP containers built from sources that pre-date the RPC client changes will still make the old call with the `android` parameter. Original change's description: > Reland "[autotest] Delete Android from stable version RPC." > > This reverts commit 5fc1314f94de8f3b6e9bdfc724052e6466e97ffe. > > Reason for revert: All clients have now been upgraded to use > the new RPC interface. No extant client should still be using > the `android` flag. So, it should now be safe to reland this. > > Original change's description: > > Revert "[autotest] Delete Android from stable version RPC." > > > > This reverts commit 8725202f94b5b0e386d0970d53d527893656fe27. > > > > Reason for revert: This made an RPC change that was not backwards > > compatible, breaking callers from before CL:1128452 > > > > Original change's description: > > > [autotest] Delete Android from stable version RPC. > > > > > > This deletes support for getting Android versions via the > > > get_stable_version() RPC. > > > > > > BUG=chromium:834335 > > > TEST=Run the stable_version command on a local instance > > > > > > Change-Id: I87aadb6330fc631e3e92c21bd39ddd1c0e9b0f60 > > > Reviewed-on: https://chromium-review.googlesource.com/1128453 > > > Commit-Ready: Richard Barnette <jrbarnette@chromium.org> > > > Tested-by: Richard Barnette <jrbarnette@chromium.org> > > > Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org> > > > > BUG=chromium:864165 > > > > Change-Id: I97d093bf548ebf776804c19c15b416e6b311d8e6 > > Reviewed-on: https://chromium-review.googlesource.com/1138913 > > Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org> > > Tested-by: Prathmesh Prabhu <pprabhu@chromium.org> > > Bug: chromium:864165 > Change-Id: Iba41cbad43f2af4e2ccfdae71875b064e5b9f0a0 > Reviewed-on: https://chromium-review.googlesource.com/1150460 > Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> > Tested-by: Richard Barnette <jrbarnette@chromium.org> > Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org> Bug: chromium:864165 Change-Id: I3e8cc7d1153c72e6db414a3c41742caecfaf5d42 Reviewed-on: https://chromium-review.googlesource.com/1162241 Commit-Queue: Richard Barnette <jrbarnette@chromium.org> Tested-by: Richard Barnette <jrbarnette@chromium.org> Reviewed-by: Richard Barnette <jrbarnette@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.