The easiest way to run tests is simply run
runtest will build the test project and push the APK to the connected device. It will then run the tests on the device. See
runtest --help for options to specify individual test classes or methods.
WARNING: You have to build the components under test (wifi-service, etc) first before you run runtest for changes there to take effect. You can use the following command from your build root to build the wifi service and run tests.
mmma frameworks/opt/net/wifi/tests && runtest frameworks-wifi
If you manually build and push the test APK to the device you can run tests using
adb shell am instrument -w 'com.android.server.wifi.test/android.support.test.runner.AndroidJUnitRunner'
Tests can be added by adding classes to the src directory. JUnit4 style test cases can be written by simply annotating test methods with
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
If you would like to collect code coverage information you can run the
coverage.sh script located in this directory. It will rebuild parts of your tree with coverage enabled and then run the tests, similar to runtest. If you have multiple devices connected to your machine make sure to set the
ANDROID_SERIAL environment variable before running the script. You must supply an output directory for results. By default the results are generated as a set of HTML pages. For example, you can use the following from the root out your source tree to generate results in the wifi_coverage directory