Closed Bug 963426 Opened 10 years ago Closed 6 years ago

Add test cases for bug 960741, messages app fails to upgrade database after updating from v1.2 to v1.3

Categories

(Firefox OS Graveyard :: RIL, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:-)

RESOLVED WONTFIX
blocking-b2g -

People

(Reporter: vicamo, Unassigned)

References

Details

+++ This bug was initially created as a clone of Bug #960741 +++

After bug 940884, we may create an separate MobileMessageDB instance in test scripts.  I think we can have following test cases implemented:

1) v1.1 -> v1.3+, without MMS
  1.1) create a mmdb with db version 12,
  1.2) populate some SMS messages by hand,
  1.3) close that mmdb,
  1.4) re-open that mmdb with version 14.

2) v1.1 -> v1.3+, with MMS
  2.1 - 2.4) same as 1.1 - 1.4), but with MMS messages,
  2.5) verify deliveryInfo property is correctly installed in all MMS messages.

3) v1.2 -> v1.3+, without MMS
  3.1) create a mmdb with db version 12,
  3.2) populate some SMS messages by hand,
  3.3) close that mmdb,
  3.4) override |MobileMessageDB.ensureDB| to run |upgradeSchema13| for version 12,
  3.5) re-open that mmdb with version 13,
  3.6) close that mmdb again,
  3.7) re-open that mmdb with non-overridden MobileMessageDB to version 14

4) v1.2 -> v1.3+, with MMS
  4.1 - 4.7) same as 3.1 - 3.7), but with MMS messages,
  4.8) verify deliveryInfo property is correctly installed in all MMS messages.
Put this bug into backlog.
blocking-b2g: --- → backlog
blocking-b2g: backlog → -
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.