| commit | b266fbab195bb8376c85cd1717a1a1376c8e6bb4 | [log] [tgz] |
|---|---|---|
| author | David Zeuthen <zeuthen@google.com> | Tue Aug 08 19:18:34 2017 +0000 |
| committer | android-build-merger <android-build-merger@google.com> | Tue Aug 08 19:18:34 2017 +0000 |
| tree | 0cffe38491f500d4d1c8ddb03c4c77733d50c462 | |
| parent | 5fec07da3d0d8a146c34150271623d92f48925ab [diff] | |
| parent | ade231287b134d714293578957977a701fbe1ec5 [diff] |
Merge "update_verifier: Support androidboot.veritymode being empty or 'disabled'." am: 399ce66534 am: bb8d04cd3c am: f2a8eba23c am: ade231287b Change-Id: I2bba85188ae59d63f018b2b70b8e15c50e07de51
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.