Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / autotest / 5dab08c529d9a914665cea9c542b51765e264bf5
commit5dab08c529d9a914665cea9c542b51765e264bf5[log] [tgz]
authorPrathmesh Prabhu <pprabhu@chromium.org>Thu Jan 12 11:16:56 2017 -0800
committerchrome-bot <chrome-bot@chromium.org>Wed Jan 18 19:19:27 2017 -0800
treeb8822b3777e8be7d23c6383574d272280693aa33
parentc018197c8f4bd6843a0b2ca1f10157dbb3ff6e48 [diff]
run_pylint: Add site-packages/ to blacklist.

Stuff in site-packages does not conform to autotest coding style and
should be ignored.

BUG=None.
TEST=None.

Change-Id: I8d24691d2ce606ea89e3f99c6e5b16e39a59a2dd
Reviewed-on: https://chromium-review.googlesource.com/427410
Commit-Ready: Prathmesh Prabhu <pprabhu@chromium.org>
Tested-by: Prathmesh Prabhu <pprabhu@chromium.org>
Reviewed-by: Shuqian Zhao <shuqianz@chromium.org>
1 file changed
tree: b8822b3777e8be7d23c6383574d272280693aa33
  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