949064 - [meta] test forward migration pathways

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia, defect)

Comment 1

[Dietrich Ayala (:dietrich)]

Should ensure forward migration pathways for all releases are in automated testing.

Comment 2

[Tony Chung [:tchung]]

Thanks for starting this, Dietrich.  

Initial thoughts:
- developers to add unit tests for update paths to each of the Apps that store profile data.   (email, call logs, contact info, calendar, system settings, etc..)
** This would run on Travis and TBPL.
- determining a matrix for update scenarios.   Currently QA, only covers data migration testing from 1.0.1 -> 1.1, and 1.1 -> 1.2.    Future Testing scenarios could include:
** 1.0.1 -> 1.1 -> 1.2 -> 1.3 -> 1.next?
** 1.0.1 --> 1.next? 
** possibly downgrade paths like reverting a version?
- Testing via FOTA update path, which may writes to a different partition.  Current testing is via OTA and pushing files via ADB.

Comment 3

[Tony Chung [:tchung]]

More thoughts:
** also minor updates to be looked into.  (ie. 1.1 -> 1.1.1)
** working closely to integrate FOTA testing with OEMs.   Given OEMs will host and often build their own update system, sharing and understanding test scenarios collaboration is important.
** defining how to handle data migration bugs, especially if they are hardware/firmware dependent.

Comment 4

[Stephen Donner [:stephend] Not actively reading bugmail]

See also, for history, bug 826450.  Although we had Marshall for a while, I believe we were close -- but not done -- with getting this running on Unagis.  Maybe/hopefully! we can resurrect that work.  As long as it's not disruptive, I don't mind one node in our infra running an update test, but I want to ensure it doesn't cause or get affected by other potential stability issues with our flashing scripts.

Comment 5

[BMO Automation]

Firefox OS is not being worked on