5d8b53b248
Move recovery-refresh/persist tests out because these tests need special steps to run. Also switch the constants to std::string. Test: recovery_manual_test passed on an A/B device Change-Id: I60b3ec6f094044945c3aafc1fae540896a6ddea6
42 lines
1.3 KiB
Markdown
42 lines
1.3 KiB
Markdown
The Recovery Image
|
|
==================
|
|
|
|
Quick turn-around testing
|
|
-------------------------
|
|
|
|
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
|
|
|
|
Running the tests
|
|
-----------------
|
|
# 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
|
|
|
|
Running the manual tests
|
|
------------------------
|
|
|
|
`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.
|