OTA Update testing script
This is something important. We should build a minor dummy update after each OTA, with just a version number bump (and something else which is noticeable) to test the OTA Updater. The app itself, and then to application of an update.
Any breakage in the build can be fixed by creating a new update, but that new update can be installed only when the OTA Updater is working fine.
Can automate this with a script.
The process
- Create normal OTA builds as usual
- Sign them normally,
sign.sh
- Install the above created build, -testing
- Create a completely new build from the same source code (make sure the build number differs)
- Sign them using
sign-test.sh
, which creates just the OTA and skips factory image and OTA generation. - Put new build on the server as -otatest
- Set that channel on device, and see if it the update works.
This ensures that the update capability of every single build we put out works.
Edited by Chirayu Desai