Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / autotest / 1de0e928b0ac1f129770b46222cf1b2465d44727
commit1de0e928b0ac1f129770b46222cf1b2465d44727[log] [tgz]
authorDaniel Hung-yu Wu <hywu@chromium.org>Fri Sep 08 14:05:14 2017 +0800
committerchrome-bot <chrome-bot@chromium.org>Fri Sep 08 17:36:03 2017 -0700
tree5e666d49b93460e129febfa695d5973e9e261147
parent9f6691d60e30df004fe0c3b6099913372fd4be90 [diff]
autotest: add camera_HAL3Perf to the perf dashboard

BUG=b/32689987
TEST='python perf_uploader_unittest.py'

Change-Id: If9452c2ff84ef4c97f6d1db5d4bcea93eb6109f5
Reviewed-on: https://chromium-review.googlesource.com/656872
Commit-Ready: Hung-yu Wu <hywu@chromium.org>
Tested-by: Hung-yu Wu <hywu@chromium.org>
Reviewed-by: Heng-ruey Hsu <henryhsu@chromium.org>
1 file changed
tree: 5e666d49b93460e129febfa695d5973e9e261147
  1. apache/
  2. bin/
  3. cli/
  4. client/
  5. contrib/
  6. database/
  7. docs/
  8. frontend/
  9. logs/
  10. results/
  11. scheduler/
  12. server/
  13. site_utils/
  14. skylab_migration/
  15. test_suites/
  16. tko/
  17. utils/
  18. venv/
  19. MODULE_LICENSE_LGPL ⇨ LGPL_LICENSE
  20. NOTICE ⇨ LICENSE
  21. .gitignore
  22. .quickmerge_sentinel
  23. __init__.py
  24. COMMIT-QUEUE.ini
  25. common.py
  26. global_config.ini
  27. LGPL_LICENSE
  28. LICENSE
  29. metadata.chromium
  30. moblab_config.ini
  31. PRESUBMIT.cfg
  32. README.md
  33. 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