Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / autotest / b6296d1c6aa86e4cd488bec4d12fe4491033cd17
commitb6296d1c6aa86e4cd488bec4d12fe4491033cd17[log] [tgz]
authorDan Shi <dshi@google.com>Thu Nov 03 15:33:56 2016 -0700
committerchrome-bot <chrome-bot@chromium.org>Sun Nov 06 01:46:39 2016 -0800
treecb31a1d7d4c10e9a65ef57e520ba8bdc0ca44b02
parentb5b8b4f981036971c619b26956c8847140eabd35 [diff]
[autotest] Change suite_scheduler.ini to be deployed by puppet

This way we don't need a push to prod to update suite_scheduler.ini change.

BUG=b:31860543
TEST=None

Change-Id: I0bdd17d4e1db42bad51769801d585f091127c629
Reviewed-on: https://chromium-review.googlesource.com/407439
Commit-Ready: Dan Shi <dshi@google.com>
Tested-by: Dan Shi <dshi@google.com>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
2 files changed
tree: cb31a1d7d4c10e9a65ef57e520ba8bdc0ca44b02
  1. apache/
  2. cli/
  3. client/
  4. contrib/
  5. database/
  6. docs/
  7. frontend/
  8. logs/
  9. packages/
  10. puppylab/
  11. results/
  12. scheduler/
  13. server/
  14. site_utils/
  15. test_suites/
  16. tko/
  17. utils/
  18. MODULE_LICENSE_LGPL ⇨ LGPL_LICENSE
  19. NOTICE ⇨ LICENSE
  20. .gitignore
  21. .quickmerge_sentinel
  22. __init__.py
  23. COMMIT-QUEUE.ini
  24. common.py
  25. global_config.ini
  26. LGPL_LICENSE
  27. LICENSE
  28. metadata.chromium
  29. moblab_config.ini
  30. PRESUBMIT.cfg
  31. README.md
  32. 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