|author||Cheng-Yi Chiang <email@example.com>||Wed Sep 14 05:24:53 2016 +0800|
|committer||ChromeOS Commit Bot <firstname.lastname@example.org>||Mon Dec 19 09:57:47 2016 +0000|
[autotest] audio_analysis: Improve peak detection The peak detection algorithm was poorly written so the performance was really bad. It took more than 20 minutes to finish analysis of 60 seconds data. Improve the algorithm to speed up peak detection. Also, add the logging format in unittest to check the timestamp. BUG=chromium:645666 TEST=run audio_analysis_unittest and see the improvement in comparison with dummy implementation. ./client/cros/audio/audio_analysis_unittest.py SpectralAnalysisTest.testPeakDetectionLarge 2016-09-14 08:51:21,328 - root - DEBUG - Test large array using dummy peak detection 2016-09-14 08:51:22,516 - root - DEBUG - Test large array using improved peak detection 2016-09-14 08:51:22,944 - root - DEBUG - Compare the result . ---------------------------------------------------------------------- Ran 1 test in 1.631s The dummy implementation took 1.2 seconds, while improved implementation took 0.4 seconds. Change-Id: I019eb7271dd68ddd11751df60748b6841d9bcb12 Reviewed-on: https://chromium-review.googlesource.com/385079 Commit-Ready: Cheng-Yi Chiang <email@example.com> Tested-by: Cheng-Yi Chiang <firstname.lastname@example.org> Reviewed-by: Wai-Hong Tam <email@example.com> (cherry picked from commit 47ab82af074d76fc390f1b088118c6d48776ced6) Reviewed-on: https://chromium-review.googlesource.com/422123 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.