Stainless green: Move waiting for interrupt to server test.

We are hitting a problem where the update is finished before we can
start the interruption. This is likely happening because we wait for
the progress to be reached in the client test and then then need to
wait for control to come back to the server test. By ending the client
test early we should have lots of time to wait for the progress in the
server test.

Add some extra info to other failures to help debug.


Change-Id: If2f891aa95020fc3de7710575ce770bf1caec4b1
Tested-by: David Haddock <>
Reviewed-by: Amin Hassani <>
Reviewed-by: Kyle Shimabukuro <>
Commit-Queue: David Haddock <>
(cherry picked from commit 5fbb073d8590534ab351f133c487d8d87e3cc95c)
Reviewed-by: David Haddock <>
2 files changed
tree: 594a45f26307a2c1cbfa142cc795dfeb813f23f5
  1. bin/
  2. cli/
  3. client/
  4. contrib/
  5. database/
  6. docs/
  7. frontend/
  8. logs/
  9. results/
  10. server/
  11. site_utils/
  12. test_suites/
  13. tko/
  14. utils/
  15. venv/
  16. .gitignore
  17. .style.yapf
  23. global_config.ini
  27. moblab_config.ini
  28. PRESUBMIT.cfg
  30. ssp_deploy_config.json

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