commit | 1b83e7e28dcdc6e670b8406d7bde115ed9371fca | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Fri Dec 23 17:30:12 2016 +0000 |
committer | android-build-merger <android-build-merger@google.com> | Fri Dec 23 17:30:12 2016 +0000 |
tree | e70c51beecac505ebbbbcf5e04d0a8816fa71a1f | |
parent | baf422229d36cb2ac278c874c17f485af2826546 [diff] | |
parent | f24d2a6b397070872f33487536063a0c5905fc64 [diff] |
Merge "tests: Add test coverage for DirUtil." am: f24d2a6b39 Change-Id: I624cb64464427d06d2711f3b88ec94cd93ac06d3
mm -j && m ramdisk-nodeps && m recoveryimage-nodeps # To boot into the new recovery image # without flashing the recovery partition: adb reboot bootloader fastboot boot $ANDROID_PRODUCT_OUT/recovery.img
# After setting up environment and lunch. mmma -j bootable/recovery # Running the tests on device. adb root adb sync data # 32-bit device adb shell /data/nativetest/recovery_unit_test/recovery_unit_test adb shell /data/nativetest/recovery_component_test/recovery_component_test # Or 64-bit device adb shell /data/nativetest64/recovery_unit_test/recovery_unit_test adb shell /data/nativetest64/recovery_component_test/recovery_component_test
recovery-refresh
and recovery-persist
executables exist only on systems without /cache partition. And we need to follow special steps to run tests for them.
Execute the test on an A/B device first. The test should fail but it will log some contents to pmsg.
Reboot the device immediately and run the test again. The test should save the contents of pmsg buffer into /data/misc/recovery/inject.txt. Test will pass if this file has expected contents.