[autotest] Stop CRAS before running Aplay test

If we run Aplay test while another stream is playing in CRAS, Aplay
won't get audio device so that it will return error. We should stop
CRAS first to make sure this situation will not happen.

TEST=Aplay test can pass reliably on peppy and lulu.

Change-Id: If50008492b5e889ba3e44117d71367cc70a5b335
Previous-Reviewed-on: https://chromium-review.googlesource.com/1175710
(cherry picked from commit 96fe31dc33a73b03eed4ed3744d94b546f862c92)
Reviewed-on: https://chromium-review.googlesource.com/1221326
Reviewed-by: Cheng-Yi Chiang <cychiang@chromium.org>
Commit-Queue: Cheng-Yi Chiang <cychiang@chromium.org>
Commit-Queue: Yu-Hsuan Hsu <yuhsuan@chromium.org>
Tested-by: Cheng-Yi Chiang <cychiang@chromium.org>
Tested-by: Yu-Hsuan Hsu <yuhsuan@chromium.org>
1 file changed
tree: 1fc92c05173840a788e6e3eae0694afd2b8e1d9f
  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. .gitignore
  21. .quickmerge_sentinel
  22. .style.yapf
  23. __init__.py
  24. COMMIT-QUEUE-moblab-pre-cq-only.ini
  25. COMMIT-QUEUE.ini
  26. common.py
  27. global_config.ini
  30. metadata.chromium
  31. moblab_config.ini
  32. PRESUBMIT.cfg
  33. README.md
  34. 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 https://chromium.googlesource.com/chromiumos/third_party/autotest

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/build_externals.py to set up the dependencies for pre-upload hook tests.

Setting up Lucifer

Setting up Lucifer