Files
frameworks_base/wifi/tests
Ecco Park 3f94ad15cd Passpoint: add FQDN and Provider name field in WifiInfo
As part of new Passpoint UX, quick Setting and "Network &* internet"
screen of Settings needs to present Provider name when Passpoint AP is
connected instead of displaying SSID of the AP.

In addition, Wifi Picker needs to match current passpoint connection
info with Passpoint AccessPoint by FQDN.

So, the two fields are added in WifiInfo

Bug: 124462043
Test: ./frameworks/base/wifi/tests/runtests.sh
Test: Tested with Passpoint AP and confirmed that the info is set
correctly.
Change-Id: I7215cba671e1c7eb07fbacb9d546d810cc26e826
Signed-off-by: Ecco Park <eccopark@google.com>
2019-02-15 10:16:12 -08:00
..

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:

  1. rebuild the framework library 'make -j32'
  2. sync over the updated library to the device 'adb sync'
  3. 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:

  1. adb disable-verity
  2. adb reboot
  3. 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/androidx.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.