commit | c844c06faf92d2250a0f0b4ec8aab97ebfd5b747 | [log] [tgz] |
---|---|---|
author | Tao Bao <tbao@google.com> | Wed Dec 28 15:15:55 2016 -0800 |
committer | Tao Bao <tbao@google.com> | Tue Jan 03 17:51:30 2017 -0800 |
tree | 41d25433af219932a7c4ec4884c36d85b4969515 | |
parent | 71633ebfb00103dd95a82cd813824dbddd9b905d [diff] |
updater: Refactor parse_range(). Returning the parsed RangeSet directly (as opposed to using some pointer parameter) to make the code cleaner. Test: Apply an incremental with the new updater. Change-Id: I8c99e701f189eb6a3eacc0d647e5a3a85fbeb3eb
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.