Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / autotest / 66ccd27a776606629239e1e8105821cfa6cbe81e
commit66ccd27a776606629239e1e8105821cfa6cbe81e[log] [tgz]
authorMary Ruthven <mruthven@chromium.org>Tue Dec 12 17:26:49 2017 -0800
committerchrome-bot <chrome-bot@chromium.org>Wed Dec 13 00:32:19 2017 -0800
tree7835ccd010b74bcad0e08a5776bb0ca54985e0f7
parentab3735882a864cfc96e056bc2ede1e2c27f1269b [diff]
firmware_Cr50ConsoleCommands: fix ARM output

We haven't been testing on ARM in a while. Update all the output to work
with current versions.

BUG=none
BRANCH=none
TEST=run on 0.1.0:FFFF:0:10 and 0.0.24:0:0:0

Change-Id: I1cf6d1236388f4469e4ad2a60b15919102839bbd
Signed-off-by: Mary Ruthven <mruthven@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/822766
Reviewed-by: Aseda Aboagye <aaboagye@chromium.org>
2 files changed
tree: 7835ccd010b74bcad0e08a5776bb0ca54985e0f7
  1. apache/
  2. bin/
  3. cli/
  4. client/
  5. contrib/
  6. database/
  7. docs/
  8. frontend/
  9. leases/
  10. logs/
  11. results/
  12. scheduler/
  13. server/
  14. site_utils/
  15. skylab_migration/
  16. test_suites/
  17. tko/
  18. utils/
  19. venv/
  20. MODULE_LICENSE_LGPL ⇨ LGPL_LICENSE
  21. NOTICE ⇨ LICENSE
  22. .gitignore
  23. .quickmerge_sentinel
  24. __init__.py
  25. COMMIT-QUEUE.ini
  26. common.py
  27. global_config.ini
  28. LGPL_LICENSE
  29. LICENSE
  30. metadata.chromium
  31. moblab_config.ini
  32. PRESUBMIT.cfg
  33. README.md
  34. 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