| commit | c1fa31ac12706c22d0dfd3940247ab11cb5ff562 | [log] [tgz] |
|---|---|---|
| author | Wu-Cheng Li <wuchengli@google.com> | Fri Nov 10 22:28:35 2017 +0800 |
| committer | chrome-bot <chrome-bot@chromium.org> | Tue Nov 14 08:04:18 2017 -0800 |
| tree | 22c37e10ace515428f849fff244736db8021a5ea | |
| parent | 7804713e7262a70c298c9c1f8acd78c4f71f8ea8 [diff] |
audio_test_data: move AudioTestDataGenerateOnDemand files out.
- SIMPLE_FREQUENCY_LOUD_WAVE_FILE, LEFT_CHANNEL_TEST_FILE, and
RIGHT_CHANNEL_TEST_FILE are all only used once. There is no
need to put them in audio_test_data.
- AudioTestDataGenerateOnDemand are generated dynamically.
Putting them in audio_test_data does not save storage.
- Other AudioTestData in audio_test_data are static files and
do not need to call generate_file. AudioTestDataGenerateOnDemand
files are inconsistent if we put them in audio_test_data.
For example, generate_file of LEFT_CHANNEL_TEST_FILE and
RIGHT_CHANNEL_TEST_FILE is not called, which is a bug.
BUG=chromium:783534
TEST=Run audio_AudioWebRTCLoopback and
audio_LeftRightInternalSpeaker on eve.
Change-Id: I44085d754619a86a92f70c7aa17b48c4b0bcb59c
Reviewed-on: https://chromium-review.googlesource.com/763787
Commit-Ready: Wu-Cheng Li <wuchengli@chromium.org>
Tested-by: Wu-Cheng Li <wuchengli@chromium.org>
Reviewed-by: Cheng-Yi Chiang <cychiang@chromium.org>
Reviewed-by: Wu-Cheng Li <wuchengli@chromium.org>
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.
See the guides to test_that and test_droid:
See the best practices guide, existing tests, and comments in the code.
git clone https://chromium.googlesource.com/chromiumos/third_party/autotest
See the coding style guide for guidance on submitting patches.