| commit | cc15350020c236808807d0d5914328f0fed646a7 | [log] [tgz] |
|---|---|---|
| author | Allen Li <ayatane@chromium.org> | Fri Sep 15 16:08:25 2017 -0700 |
| committer | chrome-bot <chrome-bot@chromium.org> | Tue Sep 26 16:14:11 2017 -0700 |
| tree | 2a8778a17226048b8ad0ae8e9a1dcab1a384f3e4 | |
| parent | 7293470e825c84a976ad787a21cc02a1c3a7d2a6 [diff] |
[autotest] Add job_aborter Add the skeleton of job_aborter. All of the cases that job_aborter has to handle are added. Due to considerations for job_aborter that came up, existing code has been redesigned. 1. The implementation for aborting a job has been moved out. The existing design is unnecessarily complex. The abort signaling mechanism should not need to go through job_reporter and can be handled directly by job_shepherd. Since job_shepherd is written in Go, the async aspect of that will be much easier to write than the Python async that would be needed for job_reporter to play middleman. The new logic will be added to monitor_db, job_aborter, and job_shepherd; job_reporter need not play. 2. Job lease liveness is determined by fcntl locks. This is more reliable than working with pids and/or sending signals. (As a bonus, this prevents a job from being owned by two processes at the same in certain cases.) BUG=chromium:748234 TEST=Unittests Change-Id: I51cad974722e2e549e94819b6a3411d569919383 Reviewed-on: https://chromium-review.googlesource.com/676085 Commit-Ready: Allen Li <ayatane@chromium.org> Tested-by: Allen Li <ayatane@chromium.org> Reviewed-by: Prathmesh Prabhu <pprabhu@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.