1# Wi-Fi Aware Integrated (ACTS/sl4a) Test Suite 2 3This directory contains ACTS/sl4a test scripts to verify and characterize 4the Wi-Fi Aware implementation in Android. 5 6There are 4 groups of tests (in 4 sub-directories): 7 8* functional: Functional tests that each implementation must pass. These 9are pass/fail tests. 10* performance: Tests which measure performance of an implementation - e.g. 11latency or throughput. Some of the tests may not have pass/fail results - 12they just record the measured performance. Even when tests do have a pass/ 13fail criteria - that criteria may not apply to all implementations. 14* stress: Tests which run through a large number of iterations to stress 15test the implementation. Considering that some failures are expected, 16especially in an over-the-air situation, pass/fail criteria are either 17not provided or may not apply to all implementations or test environments. 18* ota (over-the-air): A small number of tests which configure the device 19in a particular mode and expect the tester to capture an over-the-air 20sniffer trace and analyze it for validity. These tests are **not** automated. 21 22The tests can be executed in several ways: 23 241. Individual test(s): `act.py -c <config> -tc {<test_class>|<test_class>:<test_name>}` 25 26Where a test file is any of the `.py` files in any of the test sub-directories. 27If a test class is specified, then all tests within that test class are executed. 28 292. All tests in a test group: `act.py -c <config> -tf <test_file>` 30 31Where `<test_file>` is a file containing a list of tests. Each of the test 32group sub-directories contains a file with the same name as that of the 33directory which lists all tests in the directory. E.g. to execute all functional 34tests execute: 35 36`act.py -c <config> -tf ./tools/test/connectivity/acts_tests/tests/google/wifi/aware/functional/functional` 37 38## Test Configurations 39The test configurations, the `<config>` in the commands above, are stored in 40the *config* sub-directory. The configurations simply use all connected 41devices without listing specific serial numbers. Note that some tests use a 42single device while others use 2 devices. In addition, the configurations 43define the following key to configure the test: 44 45* **aware_default_power_mode**: The power mode in which to run all tests. Options 46are `INTERACTIVE` and `NON_INTERACTIVE`. 47 48The following configurations are provided: 49* wifi_aware.json: Normal (high power/interactive) test mode. 50* wifi_aware_non_interactive.json: Low power (non-interactive) test mode. 51