diff options
| author | Dan Albert <danalbert@google.com> | 2015-11-06 18:17:15 -0800 |
|---|---|---|
| committer | Dan Albert <danalbert@google.com> | 2015-11-06 18:21:51 -0800 |
| commit | 6ab129be1d98ed66646feb8c39ca700e12d45bb4 (patch) | |
| tree | b8275ac7ae135fd8413d8ec2cd4861c7dfe93f16 /README.md | |
| parent | 797ec6dcaa79bdf860eddae535b8a9cdedbad1ed (diff) | |
| download | ndk-6ab129be1d98ed66646feb8c39ca700e12d45bb4.tar.gz | |
Add testing instructions to the README.
Change-Id: I34e566b0095ee4c0f574b03d6dd1eb3f9dd77ee9
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 23 |
1 files changed, 14 insertions, 9 deletions
@@ -122,12 +122,17 @@ To package the NDK for Windows or Darwin (or if more control over the packaging process is needed), invoke `build/tools/package-release.sh` directly. This process will be improved in a future commit. -Best Practices for Incremental Builds -------------------------------------- - -* Do not run `build/tools/dev-cleanup.sh` which erases all prebuilts. -* Remove the individual prebuilt directory if new build deletes files. This is - rare. -* Package NDK from prebuilt tarballs in `$PREBUILT_PATH`. It runs - `build/tools/build-docs.sh` which produces no tarball in `$PREBUILT_PATH`. -* Unpack and compare against the previous package. +Testing +------- + +Running the NDK tests requires a complete NDK package (see previous steps). The +full test suite includes tests which run on a device or emulator, so you'll need +to have adb in your path and `ANDROID_SERIAL` set if more than one +device/emulator is connected. With that package: + +```bash +$ tar xf android-ndk-$BUILD_NUM-$HOST_TAG.tar.bz2 +$ cd android-ndk-$BUILD_NUM +$ export NDK=`pwd` +$ python tests/run-all.py --abi $ABI_TO_TEST +``` |