4f17615066
On devices with multiple radio chains, each scan result could be received using different combination of the available radio chains (DBS, MCC). Add a new parameter in the scan result to convey this meta information about the scan result. Bug: 68335251 Test: Unit tests Change-Id: I1fc97745b9e74b768b67b0c80e52ce4a13e69527
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.