234
edits
Software Update:HowToTestMajorUpdateUI: Difference between revisions
Jump to navigation
Jump to search
Software Update:HowToTestMajorUpdateUI (view source)
Revision as of 01:08, 13 January 2007
, 13 January 2007→create a "fake" updates.xml file on your local machine
(How To Test the Major Update UI) |
|||
| Line 1: | Line 1: | ||
Here's the quick and dirty way to test Major Update UI, specifically the detailsURL attribute and the licenseURL attributes (specified at [[Software_Update:updates.xml_Format]]). | Here's the quick and dirty way to test Major Update UI, specifically the detailsURL attribute and the licenseURL attributes (specified at [[Software_Update:updates.xml_Format]]). | ||
== create a "fake" updates.xml file on your local machine == | == Step 1: create a "fake" updates.xml file on your local machine == | ||
A "fake" updates.xml file looks like this: | A "fake" updates.xml file looks like this: | ||
| Line 14: | Line 14: | ||
</pre> | </pre> | ||
'''Important Note''' https://bugzilla.mozilla.org/attachment.cgi?id=242833 is a special, 54 byte, empty mar that does nothing to your build if you install it. So use this when testing the UI. | |||
'''Important Note''' the licenseURL and detailsURL attributes need to be http:// or https:// urls, and can not be file:// urls. | |||
== configure your prefs to point at the "fake" update.xml file == | == configure your prefs to point at the "fake" update.xml file == | ||