a1dff77196
1. Add public API to close a Channel and allow configuration to be
cleaned-up. Actual clean-up will only happen when the last p2p
client executes close or terminates (binder death is triggered
for the service).
2. Add Close Guard to verify that API is called - issue warning
otherwise. Note that to actually get the warning an app needs
to use the StrictMode policy:
StrictMode.setVmPolicy(new StrictMode.VmPolicy.Builder()
.detectLeakedClosableObjects().build());
Bug: 37443149
Test: (new) unit tests, CtsVerifier, Settings/WFD app
Change-Id: I9590101ef7f7ba0a90812634ac1b931d1482fe72
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.