| commit | 4c7c3000238ffa2e942c38a9f5076412e631a2d1 | [log] [tgz] |
|---|---|---|
| author | Kazuhiro Inaba <kinaba@chromium.org> | Mon Feb 26 16:07:01 2018 +0900 |
| committer | chrome-bot <chrome-bot@chromium.org> | Tue Feb 27 07:32:05 2018 -0800 |
| tree | d46f18230dbea81a4a9468edaccb96893b687dea | |
| parent | c3c757c9f0b18ad0c991b4025b350055ca917096 [diff] |
tradefed_test: Simplify log collection by using symlinks. Previously we copied the results and logs from the tradefed's directory to where our tools can recognize. This CL simplifies the steps by introducing symlinks from the former to the latter. Advantages are: * Less code, hence less bugs. We no more need to parse stdout for obtaining the directory name, nor to run explicit tree copying. * (Partial) log collection even in the case of aborted tradefed runs. By using symlinks instead of copy-after-finish, as long as tradefed flushes out, the logs upto the point of timeout abort etc can be collected. The logs are, even if they are partial, useful for debugging. Drawbacks are we rely on an internal implementation of the tradefed tool that it can transparently deals with symlinks injected at this location. That said, it is working well for current cheets_CTS_N, cheets_CTS_P, and cheets_GTS, and since we are anyway relying on the directory structures, etc, the new assumption won't be a big deal. BUG=b:73136256 TEST=run some cheets_CTS_N tests with/without manually shortening the timelimit Change-Id: I6c101e94ee9ede15f6cd38e29ecb2d974de20c15 Reviewed-on: https://chromium-review.googlesource.com/937144 Commit-Ready: Kazuhiro Inaba <kinaba@chromium.org> Tested-by: Kazuhiro Inaba <kinaba@chromium.org> Reviewed-by: Ilja H. Friedel <ihf@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.
You need to run utils/build_externals.py to set up the dependencies for pre-upload hook tests.