AUS:Tests

Existing Tools

These need to be consolidated into a more complete single testing suite:

• AUS acceptance tests
• cf's output comparison
  • Good visualization idea, good coverage, but only for nightlies
• morgamic's output comparison
  • Has selection of different options and AUS2 sources (prod, stage, etc.) as well as a dynamic report that is saved and logged
• rhelmer/davel's update tests
  • Has better coverage per-test -- downloads .mar and compares hashes. Notifies if there is a 404 or hash mismatch.
  • l10n tests

Inputs

• uri version
• product
• version
• build
• platform
• locale
• channel

Outputs

• See Software Update XML format definition

Example:

<?xml version="1.0"?>
<updates>
    <update type="minor" version="1.5.0.7" extensionVersion="1.5.0.7" buildID="2006083105" >
        <patch type="complete" URL="http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2006-08-31-05-mozilla1.8.0/firefox-1.5.0.7.en-US.mac.complete.mar" hashFunction="md5" hashValue="90f58b8836f288d42e2c14ea5ba3c71e" size="15408802"/>
        <patch type="partial" URL="http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2006-08-30-05-mozilla1.8.0/firefox-1.5.0.7.en-US.mac.partial.2006083005-2006083105.mar" hashFunction="MD5" hashValue="712b418e5c300be941515d5f75eb167f" size="6859"/>
    </update>
</updates>

AUS Flow

To learn a little about what logic determines what XML is displayed, see the AUS flow chart.

Test Assumptions

Sets of rules we can use to make our tests easier:

• For a given product, platform and locale, the output for all possible combinations having buildID more than one-off the latest will be identical
• One-off buildID offerings will have an added partial update that points to the latest build.