| commit | b3014bc08f3dcd9f9050b50f617416d130430498 | [log] [tgz] |
|---|---|---|
| author | Kyle Shimabukuro <kyleshima@chromium.org> | Fri Jan 24 13:26:40 2020 -0800 |
| committer | Commit Bot <commit-bot@chromium.org> | Sun Jan 26 08:48:49 2020 +0000 |
| tree | 0c45efea95f5372f94c492aa71d0acaeb25f44c5 | |
| parent | bfb7d73fdd9ef1aa1b4456aefb2b99e936f7c9af [diff] |
Fix for failing RLZ tests. RLZ autotests have been failing due to the RLZ ping not being sent properly. The RLZ ping is sent after a delay prescribed by the --rlz_ping_delay flag, which is set in /etc/chrome_dev.conf. However, inspecting chrome://version during test execution showed that the flag was not set, even though it was properly set before the device rebooted and logged in as the test user. If the flag is not set, I think the default delay is 24 hours, and the test times out after 2 minutes. Furthermore, the contents of /etc/chrome_dev.conf during test execution are different from what was set by the test in rlz_CheckPing.py. It seems that the test runner modifies this file to contain only the flag CHROME_HEADLESS=1. I worked around this by setting the --rlz_ping_delay flag through chrome.Chrome()'s extra_browser_args optional parameter. BUG=chromium:1045615 TEST=rlz_CheckPing, rlz_CheckPing.guest locally Change-Id: I035fe87eb84c3e19b259d322b545d07d0a4f1bf8 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/2021022 Reviewed-by: David Haddock <dhaddock@chromium.org> Tested-by: Kyle Shimabukuro <kyleshima@chromium.org> Commit-Queue: David Haddock <dhaddock@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.