commit | 953851cb97d70f0bfa6e967824d1ff3f104966b6 | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Sun Nov 20 05:18:19 2016 +0000 |
committer | android-build-merger <android-build-merger@google.com> | Sun Nov 20 05:18:19 2016 +0000 |
tree | ffb64050202d1e3204ddcef82cfa71a430f6b9e6 | |
parent | 723b5d505f286ce1704f8f8b316d47270f99b1e8 [diff] | |
parent | 062a2cffb375fe87bc8e088122491c854bc6a0ee [diff] |
Merge "updater: Refactor set_stage() and get_stage() functions." am: c627cd6486 am: 146f92ab3e am: 062a2cffb3 Change-Id: I4673e6b160fcf9e2b6069af91eeae97d4e4a17ed
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.