Should I test my app-update before release? #110
-
|
I've created a new version of my app. Should I test the update-cycle before releasing the new version? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Yes. Before releasing a new version of your app, it is very important to test your app's update cycle thoroughly. If you don't test, and something does go wrong, e.g. due to a misconfiguration or a bug in your app or in tufup, your users may need to re-install your app from scratch. Testing the update cycle is especially important if your new app release includes a new version of tufup. The app update cycle is illustrated in the test_update_cycle script in tufup-example. We recommend doing at least two local test-releases whenever the tufup version has been upgraded in your app. For example, suppose your app v1.0 uses tufup 0.5.2, and you are planning a new release, your app v2.0, which uses tufup 0.6.0. In this case you should create a temporary test release, e.g. v2.1, which is identical to v2.0 except for the version. Then you can test the update cycle in two steps:
The test releases can be hosted on localhost, as described tufup-example. |
Beta Was this translation helpful? Give feedback.
Yes. Before releasing a new version of your app, it is very important to test your app's update cycle thoroughly.
If you don't test, and something does go wrong, e.g. due to a misconfiguration or a bug in your app or in tufup, your users may need to re-install your app from scratch.
Testing the update cycle is especially important if your new app release includes a new version of tufup.
The app update cycle is illustrated in the test_update_cycle script in tufup-example.
We recommend doing at least two local test-releases whenever the tufup version has been upgraded in your app.
For example, suppose your app v1.0 uses tufup 0.5.2, and you are planning a new release, your app v2.0, which u…