History

Ecco Park 84d601fbda passpoint-r1: fix the wrong filed for PPS-MO.

Currently Passpoint-r1 follows the PPS-MO format to install passpoint
profile.

Howevever, one field(SubscriptionParameter) is not correct.
Normally passpoint-r1 doesn't use this field because this is used for
passpoint-r2 feature.
So, currently there is no issue with wrong field for using passpoint-r1.

But, it needs to be "SubscriptionParameters" according to the hostpot2.0
release 2.0 techinical specification.

Bug: 111449001
Test:  ./frameworks/base/wifi/tests/runtests.sh
Change-Id: Idb6bb4d28913bd3d0905b330e25fbb20b99bbf2e
Signed-off-by: Ecco Park <eccopark@google.com>

2018-07-14 00:11:20 +00:00

assets

passpoint-r1: fix the wrong filed for PPS-MO.

2018-07-14 00:11:20 +00:00

src/android/net/wifi

Merge "[RTT] Update RTT preamble selection algorithm" into pi-dev am: 51f3c4481c

2018-05-06 21:16:57 -07:00

Android.mk

Merge "Remove duplicate definitions of utility variables" am: 8d5a39ac62

2018-04-04 17:56:57 -07:00

AndroidManifest.xml

…

AndroidTest.xml

Exempt tests for hidden APIs.

2018-04-06 14:54:39 +01:00

README.md

…

runtests.sh

update wifi unit test script

2018-04-23 15:54:36 -07:00

README.md

Wifi Unit Tests

This package contains unit tests for the android wifi framework APIs based on the Android Testing Support Library. The test cases are built using the JUnit and Mockito libraries.

Running Tests

The easiest way to run tests is simply run

frameworks/base/wifi/tests/runtests.sh

runtests.sh will build the test project and all of its dependencies and push the APK to the connected device. It will then run the tests on the device.

To pick up changes in framework/base, you will need to:

rebuild the framework library 'make -j32'
sync over the updated library to the device 'adb sync'
restart framework on the device 'adb shell stop' then 'adb shell start'

To enable syncing data to the device for first time after clean reflash:

adb disable-verity
adb reboot
adb remount

See below for a few example of options to limit which tests are run. See the AndroidJUnitRunner Documentation for more details on the supported options.

runtests.sh -e package android.net.wifi
runtests.sh -e class android.net.wifi.WifiScannerTest

If you manually build and push the test APK to the device you can run tests using

adb shell am instrument -w 'android.net.wifi.test/android.support.test.runner.AndroidJUnitRunner'

Adding Tests

Tests can be added by adding classes to the src directory. JUnit4 style test cases can be written by simply annotating test methods with org.junit.Test.

Debugging Tests

If you are trying to debug why tests are not doing what you expected, you can add android log statements and use logcat to view them. The beginning and end of every tests is automatically logged with the tag TestRunner.