Thanks for the reminder Huburt! Any time a schema or public datastructure changes in a backwards incompatible way, the patch should come with a unit test that mocks the old data and tests the migration path.
We've got a metabug for corralling migration tests here: https://bugzilla.mozilla.org/show_bug.cgi?id=949064 And there's a conversation going on with QA about covering these scenarios, and also with Zac Campbell about what we can do to use the existing UI tests to catch migration problems that cause major breakage. Ultimately though, the only scalable way to do it is for developers to be responsible for ensuring compatibility across releases by writing code and tests to cover migration. On Fri, Dec 13, 2013 at 12:54 AM, Hubert Lu <h...@mozilla.com> wrote: > Dear all, > This is a friendly reminder. Please consider the data migration cases for > your app. > For example, when device is updated via OTA/FOTA, the data should migrate > well. > That is to say, you could consider things like different database schema > or different webapi structure. > Thanks a lot. > > Best Regards, > Hubert Lu > --- > QA Engineer, MoCo Taiwan > Tel: +886-2-87861100 ext.343 > > _______________________________________________ > dev-gaia mailing list > dev-g...@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-gaia _______________________________________________ dev-b2g mailing list dev-b2g@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-b2g
