|author||Yuta Hijikata <email@example.com>||Wed Oct 07 04:31:30 2020 +0000|
|committer||Commit Bot <firstname.lastname@example.org>||Wed Oct 07 08:38:52 2020 +0000|
Revert "Put name of in-progress test in crash metadata." This reverts commit 20e1936de1ba7cbb7cb3811d2e277c188098c51c. Reason for revert: The change seems to break Android PFQ due to lack of permission. The line causing the error is client/common_lib/test.py:399. https://ci.chromium.org/p/chromeos/builders/general/PFQ/b8867149612828084176? ``` 19:47:27 INFO | autoserv| File "/build/betty-pi-arc/usr/local/build/autotest/client/common_lib/test.py", line 399, in _call_run_once 19:47:27 INFO | autoserv| os.mkdir(crash_run_dir, 0755) 19:47:27 INFO | autoserv| OSError: [Errno 13] Permission denied: '/run/crash_reporter' ``` Original change's description: > Put name of in-progress test in crash metadata. > > When we start uploading crashes from test results, it will be useful to > know during which test a crash occurred (if any). > > Also, run git cl format. > > This is a reland of https://crrev.com/c/2393262, fixed to work for > server tests. > > BUG=chromium:1119443 > TEST=test_that --board=eve $DUT logging_UserCrash\ > logging_GenerateCrashFiles > > Change-Id: I4491d45da66554cfd0a55d40dcde0f56fab5e330 > Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/2429928 > Reviewed-by: Derek Beckett <email@example.com> > Reviewed-by: Greg Edelston <firstname.lastname@example.org> > Reviewed-by: Joon Ahn <email@example.com> > Commit-Queue: Miriam Zimmerman <firstname.lastname@example.org> > Tested-by: Miriam Zimmerman <email@example.com> Bug: chromium:1119443 Change-Id: Iec2baee298557f454a8e09eb4f20396ab1a6e036 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/2454963 Reviewed-by: Jiyoun Ha <firstname.lastname@example.org> Reviewed-by: Yuta Hijikata <email@example.com> Commit-Queue: Yuta Hijikata <firstname.lastname@example.org> Tested-by: Yuta Hijikata <email@example.com>
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.
You need to run
utils/build_externals.py to set up the dependencies for pre-upload hook tests.