|author||Ilja H. Friedel <email@example.com>||Mon Oct 15 16:20:00 2018 -0700|
|committer||Ilja H. Friedel <firstname.lastname@example.org>||Tue Oct 16 03:27:14 2018 +0000|
tradefed_chromelogin: use dummy_Pass to install autotest. For unclear reason autotest is often not installed in the lab since build R71-11151.0.0. Fix our code in this situation. Instead of using cheets_StartAndroid which is ambiguous (_N and _P) use dummy_Pass client test to force install Autotest. BUG=b:117743279 TEST=delete /usr/local/autotest on DUT and run a cheets_CTS_P test. 16:17:49 INFO | autoserv| Ensure Android is running (timeout=90)... 16:17:50 INFO | autoserv| Autotest not installed, forcing install using dummy_Pass... 16:17:50 INFO | autoserv| Installing autotest on 100.90.30.47 16:17:50 INFO | autoserv| Using installation dir /usr/local/autotest 16:17:50 INFO | autoserv| Could not install autotest using the packaging system: No repos to install an autotest client from. Trying other methods 16:17:52 INFO | autoserv| Installation of autotest completed from /build/caroline-arcnext/usr/local/build/autotest/client/ 16:17:52 INFO | autoserv| Installing updated global_config.ini. 16:17:57 INFO | autoserv| Executing /usr/local/autotest/bin/autotest /usr/local/autotest/control phase 0 16:17:57 INFO | autoserv| Entered autotestd_monitor. 16:17:57 INFO | autoserv| Finished launching tail subprocesses. 16:17:57 INFO | autoserv| Finished waiting on autotestd to start. 16:17:58 INFO | autoserv| START ---- ---- timestamp=1539645479 localtime=Oct 15 16:17:59 16:18:03 INFO | autoserv| START dummy_Pass dummy_Pass timestamp=1539645484 localtime=Oct 15 16:18:04 16:18:03 INFO | autoserv| Bundling /build/caroline-arcnext/usr/local/build/autotest/client/site_tests/dummy_Pass into test-dummy_Pass.tar.bz2 16:18:05 INFO | autoserv| GOOD dummy_Pass dummy_Pass timestamp=1539645486 localtime=Oct 15 16:18:06 completed successfully 16:18:05 INFO | autoserv| END GOOD dummy_Pass dummy_Pass timestamp=1539645486 localtime=Oct 15 16:18:06 16:18:06 INFO | autoserv| END GOOD ---- ---- timestamp=1539645487 localtime=Oct 15 16:18:07 16:18:06 INFO | autoserv| Got lock of exit_code_file. 16:18:06 INFO | autoserv| Released lock of exit_code_file and closed it. 16:18:08 INFO | autoserv| Client complete 16:18:09 INFO | autoserv| END GOOD dummy_Pass dummy_Pass timestamp=1539645486 localtime=Oct 15 16:18:06 16:18:09 INFO | autoserv| Not using --dont_override_profile to start Chrome. 16:18:26 INFO | autoserv| adb -H localhost -P 5037 keygen /tmp/tmpjN4izn_cheets_ Change-Id: I57b638522cea0d204cf1f5935b482b670c8822c9 Reviewed-on: https://chromium-review.googlesource.com/c/1281846 Tested-by: Ilja H. Friedel <email@example.com> Trybot-Ready: Ilja H. Friedel <firstname.lastname@example.org> Reviewed-by: Kazuhiro Inaba <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.