|author||Cheng-Yi Chiang <email@example.com>||Thu Nov 10 16:55:47 2016 +0800|
|committer||ChromeOS Commit Bot <firstname.lastname@example.org>||Mon Dec 19 09:57:42 2016 +0000|
[autotest] audio_data: Use numpy fromstring function Use numpy fromstring function to read samples from data string. This speeds up the time to read data from large file or large data string and parse data input channel samples. The speed boost is significant. For example, for 150 seconds long data, the time to read data dropped from 140 seconds to 0.2 seconds. Also, remove some unused functions. BUG=chromium:663616 TEST=Use check_quality tool, check the time to read samples becomes much faster. Change-Id: I6a9028445b3311cd01a3c75621eaf64b5b9d11b8 Reviewed-on: https://chromium-review.googlesource.com/409893 Commit-Ready: Cheng-Yi Chiang <email@example.com> Tested-by: Cheng-Yi Chiang <firstname.lastname@example.org> Reviewed-by: Kalin Stoyanov <email@example.com> (cherry picked from commit 443d9083210bd0acd94e1e38153eb1d3a5312f90) Reviewed-on: https://chromium-review.googlesource.com/422122 Reviewed-by: Ting Shen <firstname.lastname@example.org> Commit-Queue: Ting Shen <email@example.com> Tested-by: Ting Shen <firstname.lastname@example.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
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.