History

Anton Hansson ab6ec61251 frameworks/base: Set LOCAL_SDK_VERSION where possible.

This change sets LOCAL_SDK_VERSION for all packages where
this is possible without breaking the build, and
LOCAL_PRIVATE_PLATFORM_APIS := true otherwise.

Setting one of these two will be made required soon, and this
is a change in preparation for that. Not setting LOCAL_SDK_VERSION
makes the app implicitly depend on the bootclasspath, which is
often not required. This change effectively makes depending on
private apis opt-in rather than opt-out.

Test: make relevant packages
Bug: 73535841
Change-Id: I4233b9091d9066c4fa69f3d24aaf367ea500f760

2018-02-28 15:13:23 +00:00

src/android/net/lowpan

…

Android.mk

frameworks/base: Set LOCAL_SDK_VERSION where possible.

2018-02-28 15:13:23 +00:00

AndroidManifest.xml

…

AndroidTest.xml

…

README.md

…

runtests.sh

…

README.md

LoWPAN Unit Tests

This package contains unit tests for the android LoWPAN framework System 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/lowpan/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.lowpan
runtests.sh -e class android.net.lowpan.LowpanManagerTest

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.