commit | d5c754a84f89c7668562dc347aaf3064449c64d6 | [log] [tgz] |
---|---|---|
author | Micah Morton <mortonm@chromium.org> | Wed Apr 04 10:09:47 2018 -0700 |
committer | chrome-bot <chrome-bot@chromium.org> | Thu Apr 05 22:12:18 2018 -0700 |
tree | 7545840f583531e53adc797fb40fe66fe99b0ee1 | |
parent | e97e22d92aeb13901b83ff645b1c3ef870ff3d97 [diff] |
Update test helper .py files for VPN testing. This CL is in preparation to run shill as non-root user. This CL does two things: 1) Creates /run/ipsec directory in the network chroot used for spinning up a VPN server on the DUT (for testing VPN client). This is necessary because we want to run strongSwan with compile-time config option "--with-piddir=/run/ipsec", which will allow us to use a runtime data dir that can be accessed by non-root 'ipsec' user. Currently, strongSwan uses /run for runtime data dir, which we don't want to make accessible to non-root user -- we want to use /run/ipsec instead, which we give to 'ipsec' user. 2) Removes ipsec-related modprobes from vpn_server.py, since they were recently compiled into the kernel by https://chromium.googlesource.com/chromiumos/third_party/kernel/+/12fed474fc1c00a2a7b363eb3219295bcd3a2a1d CQ-DEPEND=CL:996312 CQ-DEPEND=CL:996243 CQ-DEPEND=CL:996245 CQ-DEPEND=CL:996248 BUG=chromium:649417 TEST=network_VPNConnect.* tests pass with change. Change-Id: Ia7e91c0bd94feeb3d027838777d631578857d7fc Reviewed-on: https://chromium-review.googlesource.com/995538 Commit-Ready: Micah Morton <mortonm@chromium.org> Tested-by: Micah Morton <mortonm@chromium.org> Reviewed-by: Micah Morton <mortonm@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.