autotest: Three way Perf setup

Change the WiFi_Perf tests to ustilize the pcap device as a Netperf
endpoint in throughput testing. This setup utilizes some hard-coded
values for ethernet interface names and ip addresses for the LAN ports
on the pcap and router Gale devices. This is necessary because the
router device is not configured with the daemons to handle the
assignment automatically. This also means that some ip routes need to be
set up manually on the devices to allow traffic to move as needed.

Specific arguments for the LAN interface device names and ip addresses
may be provided at the command line. If not provided, default values
will be used instead.

The throughput results after making this change are improved as
expected, but not completely as high as expected. There is still a
bottleneck on the router CPU in some cases. In other cases, we are
measuring the total transmitted data from the source device, rather than
measuring the received data on the target device. This results in some
test cases that have artificially inflated throughput values. These
problems could all be resolved by transition from Netperf to Iperf.

This implementation uses IpConfigContextManager to make ip config
changes on the test devices. This ensures that the ip config changes are
not persisted if the test fails or is otherwise interrupted. To test
this, I exited the test at various stages and checked that the ip
configs were correcty undone.

TEST=test_that $DUT suite:wifi_perf
test_that --fast $DUT network_WiFi_Perf.vht80 --args='router_lan_ip_addr=""'

Change-Id: I940d37e8b59379d9bdc03d62390b00a7f718cc79
Commit-Queue: Kevin Lund <>
Tested-by: Kevin Lund <>
Reviewed-by: Arowa Suliman <>
1 file changed
tree: 918ac2e9f3e295671a3ee7c081dc633f788de801
  1. bin/
  2. cli/
  3. client/
  4. contrib/
  5. database/
  6. docs/
  7. frontend/
  8. logs/
  9. metadata/
  10. results/
  11. server/
  12. site_utils/
  13. test_suites/
  14. tko/
  15. utils/
  16. venv/
  17. .gitignore
  18. .style.yapf
  26. global_config.ini
  31. OWNERS
  32. PRESUBMIT.cfg
  35. ssp_deploy_config.json
  36. unblocked_terms.txt

Autotest: Automated integration testing for Android and Chrome OS Devices

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.

Run some autotests

See the guides to test_that and test_droid:

test_droid Basic Usage

test_that Basic Usage

Write some autotests

See the best practices guide, existing tests, and comments in the code.

Autotest Best Practices

Grabbing the latest source

git clone

Hacking and submitting patches

See the coding style guide for guidance on submitting patches.

Coding Style

Pre-upload hook dependencies

You need to run utils/ to set up the dependencies for pre-upload hook tests.

Setting up Lucifer

Setting up Lucifer