| commit | e1207af9ea77dfe241c14639a773449f6d07ecf5 | [log] [tgz] |
|---|---|---|
| author | Paul Hobbs <phobbs@google.com> | Wed Sep 06 19:09:13 2017 -0700 |
| committer | chrome-bot <chrome-bot@chromium.org> | Thu Oct 26 15:57:49 2017 -0700 |
| tree | 645267b22243385ec168aa17512dea534d4cc448 | |
| parent | 8873e20d5035df50e8fabd87f35bc0678467788f [diff] |
[autotest] Fix constraints in hqe_by_insert_time get_host_queue_entries_by_insert_time was showing some strange behavior because it was making a wrong assumptions about the gap between insert-time and start-time being small. - Renamed to "get_host_queue_entries_by_start_time" - Changed the API to be based on started_on constraints. - Changed the function to infer only correct insert-time constraints. This means we cannot assume any lower bound on the insert-time, because the gap between insert and start times may be arbitrarily large. - Added more unit test coverage. BUG=chromium:748209 TEST=unit tests pass. Change-Id: I60133e7a5f6431f35349c17f0644bc04e04cfcbd Reviewed-on: https://chromium-review.googlesource.com/685735 Commit-Ready: Paul Hobbs <phobbs@google.com> Tested-by: Paul Hobbs <phobbs@google.com> Reviewed-by: Paul Hobbs <phobbs@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.