902950 - Fix test TODO left over from bug 853388

Status: RESOLVED INACTIVE

(Toolkit :: Add-ons Manager, defect)

Description

[:Irving Reid (No longer working on Firefox)]

Bug 853388 left behind one unresolved test case, involving the intersection between updating addons (without changing the addon version number), rebuilding the addon database and handling compatibility overrides from AMO.

See https://bugzilla.mozilla.org/show_bug.cgi?id=853388#c31 and following comments (mostly #c32 and #c33).

My most recent thought on this issue is: If there is a compatibility update from AMO, shouldn't the cached .json file we create for the staged add-on contain that information? I'm not sure it does in this test case.

Comment 1

[Dave Townsend [:mossop]]

(In reply to :Irving Reid from comment #0)
> Bug 853388 left behind one unresolved test case, involving the intersection
> between updating addons (without changing the addon version number),
> rebuilding the addon database and handling compatibility overrides from AMO.
> 
> See https://bugzilla.mozilla.org/show_bug.cgi?id=853388#c31 and following
> comments (mostly #c32 and #c33).
> 
> My most recent thought on this issue is: If there is a compatibility update
> from AMO, shouldn't the cached .json file we create for the staged add-on
> contain that information? I'm not sure it does in this test case.

Yes it should, I'm pretty sure it does too. The question is whether that compatibility update makes it into the DB if the DB is getting rebuilt during the same startup that the add-on is getting installed.

Comment 2

[BMO Automation]

Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.