Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / autotest / dc9571ba3277e211545ff11bd3731e474f8ea6b6
commitdc9571ba3277e211545ff11bd3731e474f8ea6b6[log] [tgz]
authorPo-Hsien Wang <pwang@chromium.org>Thu Aug 10 15:49:02 2017 -0700
committerchrome-bot <chrome-bot@chromium.org>Thu Aug 10 22:47:25 2017 -0700
treeaa2cedc94c802e4a4a570fd4412f31b49700f8d1
parent73e74b0d0157ac87e63a9fdca60b31f61bd06848 [diff]
suite_scheduler: force schedule task

Let task decide whether it should be force to schedule on afe.

BUG=b:64552305
TEST=suite_scheduler --sanity
TEST=unittest

Change-Id: I30389a567418674585f0a62c32fef11119a8ff2f
Reviewed-on: https://chromium-review.googlesource.com/610456
Commit-Ready: Po-Hsien Wang <pwang@chromium.org>
Tested-by: Po-Hsien Wang <pwang@chromium.org>
Reviewed-by: Xixuan Wu <xixuan@chromium.org>
1 file changed
tree: aa2cedc94c802e4a4a570fd4412f31b49700f8d1
  1. apache/
  2. cli/
  3. client/
  4. contrib/
  5. database/
  6. docs/
  7. frontend/
  8. logs/
  9. results/
  10. scheduler/
  11. server/
  12. site_utils/
  13. test_suites/
  14. tko/
  15. utils/
  16. MODULE_LICENSE_LGPL ⇨ LGPL_LICENSE
  17. NOTICE ⇨ LICENSE
  18. .gitignore
  19. .quickmerge_sentinel
  20. __init__.py
  21. COMMIT-QUEUE.ini
  22. common.py
  23. global_config.ini
  24. LGPL_LICENSE
  25. LICENSE
  26. metadata.chromium
  27. moblab_config.ini
  28. PRESUBMIT.cfg
  29. README.md
  30. ssp_deploy_config.json
README.md

Autotest: Automated integration testing for Android and Chrome OS Devices

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.

Run some autotests

See the guides to test_that and test_droid:

test_droid Basic Usage

test_that Basic Usage

Write some autotests

See the best practices guide, existing tests, and comments in the code.

Autotest Best Practices

Grabbing the latest source

git clone https://chromium.googlesource.com/chromiumos/third_party/autotest

Hacking and submitting patches

See the coding style guide for guidance on submitting patches.

Coding Style