commit | 360aa975e747340548d9a91f65def5954e693a03 | [log] [tgz] |
---|---|---|
author | android-build-team Robot <android-build-team-robot@google.com> | Wed Oct 04 08:04:40 2017 +0000 |
committer | android-build-team Robot <android-build-team-robot@google.com> | Wed Oct 04 08:04:40 2017 +0000 |
tree | ce81f6419c38011df6d96545a783b27a6d60f357 | |
parent | be41bc6d0330dc3fb8f602d876c4de5977e44de5 [diff] | |
parent | a79c09493e2589d2ca6030a6042a2a566c641833 [diff] |
Snap for 4375922 from a79c09493e2589d2ca6030a6042a2a566c641833 to pi-release Change-Id: If5160139fb463c3156dab6e7e17c6044174bbecf
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.
ResourceTest
validates whether the png files are qualified as background text image under recovery.
1. `adb sync data` to make sure the test-dir has the images to test. 2. The test will automatically pickup and verify all `_text.png` files in the test dir.