Closed
Bug 498451
Opened 17 years ago
Closed 17 years ago
enhance updates verification script to test updates from older versions
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 408453
People
(Reporter: jbecerra, Unassigned)
Details
Currently the updates verification script tests whether we can go from the latest release version to the one we are about to ship. It tests partials+fallbacks. Could we enhance the verification script such that we test updating from at least two older versions as well?
For example: if we are testing 3.0.12, have the script verify updates going from 3.0.11->3.0.12(partial and fallback), 3.0.10->3.0.12 (complete+fallback), and at least one older one, like 3.0.older->3.0.12, perhaps randomized.
Comment 1•17 years ago
|
||
This looks like a dupe of 408453 - what do you think, juan?
And for the record, this would not have helped us catch bug 498273. Update verify does *not* use the in-app 'check for updates' code. It tests the MARs themselves, and updater.exe.
Updated•17 years ago
|
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
| Assignee | ||
Updated•13 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•