Get nebraska from git HEAD

autoupdate_EndToEndTest currently is fetching nebraska from the
devserver, but the devserver isn't being updated with new images anymore
so it's still serving an older version of nebraska. We need the latest
version to pick up fixes though, so always opt to get it from git HEAD.

TEST=test_that chromeos4-row7-rack11-host39 autoupdate_EndToEndTest --autotest_dir ~/trunk/src/third_party/autotest/files --args="update_type=delta source_release=14382.0.0 source_payload_uri=gs://chromeos-releases/dev-channel/cherry/14382.0.0/payloads/chromeos_14382.0.0_cherry_dev-channel_full_test.bin-gyywczdbha3wjkwpsipe5hzo5zbuw36i target_release=14382.0.0 target_payload_uri=gs://chromeos-releases/dev-channel/cherry/14382.0.0/payloads/chromeos_14382.0.0-14382.0.0_cherry_dev-channel_delta_test.bin-gyywczdbha3wi4pqmosksupuokistkmm"

Change-Id: I694972dd755aa5cdf6ba6c17eada90b5b750d6b6
Tested-by: Kyle Shimabukuro <>
Reviewed-by: David Haddock <>
Reviewed-by: Jae Hoon Kim <>
Reviewed-by: Derek Beckett <>
Commit-Queue: David Haddock <>
2 files changed
tree: 2f37fd4118265312dc439e9fdfbd1d878fc48d90
  1. bin/
  2. cli/
  3. client/
  4. contrib/
  5. database/
  6. docs/
  7. frontend/
  8. logs/
  9. metadata/
  10. results/
  11. server/
  12. site_utils/
  13. test_suites/
  14. tko/
  15. utils/
  16. venv/
  17. .gitignore
  18. .style.yapf
  26. global_config.ini
  31. OWNERS
  32. PRESUBMIT.cfg
  35. ssp_deploy_config.json
  36. unblocked_terms.txt

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

Hacking and submitting patches

See the coding style guide for guidance on submitting patches.

Coding Style

Pre-upload hook dependencies

You need to run utils/ to set up the dependencies for pre-upload hook tests.

Setting up Lucifer

Setting up Lucifer