| commit | 8754a1a087a9553b277829583b46f05c07beb369 | [log] [tgz] |
|---|---|---|
| author | Shuqian Zhao <shuqianz@chromium.org> | Wed Aug 24 12:54:11 2016 -0700 |
| committer | Shuqian Zhao <shuqianz@chromium.org> | Fri Aug 26 23:16:05 2016 +0000 |
| tree | d29a4b7a4fb39f15df7fafe50425f8206271d0a0 | |
| parent | d0702f329b436df58f80c6095045604ac5fab0f8 [diff] |
[autotest] modify deploy script to support test_push Modify the server deploy script to support both deploying server to prod and updating test_push servers. Changes include: 1. Rename deploy_production to deploy_server, deploy_production_local to deploy_server_local. 2. change deploy_server script to accept option, which specify it is used for prod server or test_push server. 3. change deploy_server_local to support updating test_push servers. 4. change deploy_server_local to stash the changes before update. 5. change deploy_server_local to only run update cmds when the corresponding repos/files have been changed, so need to run the cmds to deploy the changes BUG=None TEST=unittest and test on test sever. Change-Id: I2026f1f9ed0bbe5ec37363e5c01f97a94942114f Reviewed-on: https://chromium-review.googlesource.com/375139 Tested-by: Shuqian Zhao <shuqianz@chromium.org> Reviewed-by: Dan Shi <dshi@chromium.org> Commit-Queue: Shuqian Zhao <shuqianz@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.