commit | 7a890e5cf5900a1eff63de06c813475305cabc37 | [log] [tgz] |
---|---|---|
author | Elliott Hughes <enh@google.com> | Sat Jan 07 12:49:32 2017 -0800 |
committer | Elliott Hughes <enh@google.com> | Sat Jan 07 12:49:32 2017 -0800 |
tree | 26b0921cdc3e28d01293c01464656a585dbe2346 | |
parent | 91f74c82cd7518a0cbfb8239bbbc27190a1b112a [diff] |
Move to .md files for even trivial documentation. So it's automatically displayed for folks browsing the source. Bug: N/A Test: N/A Change-Id: Ie9b190072ebdf0faf06cc1fd7b3467c031056753
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.