AUS:Tests: Difference between revisions
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
== In General == | == In General == | ||
The only time I get a major offer is if: | The only time I get a major offer is if: | ||
#There is no minor update for me (I'm at the latest point release) | #There is no minor update for me (I'm at the latest point release) AND | ||
AND | |||
#I've not clicked never for this major update version | #I've not clicked never for this major update version | ||
Revision as of 00:46, 24 October 2006
To Be Tested
AUS Major/Minor Update Cases
- -1 from current minor version (i.e. I have 1.5.0.7 and 1.5.0.8 is published)
- User should get the minor update. No offer of Major will be made
- -x from current minor version (i.e. I have 1.5.0.3 and 1.5.0.8 is published)
- User should get the minor update. No offer of Major will be made
- at current minor version (I have 1.5.0.8 and the only newer version is 2.0.0.0)
- User should get the offer for major
- at current minor version (I have 1.5.0.8 and the only newer version is 2.0.0.0) and have clicked "never" to previous major update offer
- User should get no update.
- at current minor version (I have 1.5.0.8 and the only newer version is 2.0.0.0) and have clicked "never" to previous major update offer - however we've offered a new major version (i.e. 2.1)
- User should get major update offer
In General
The only time I get a major offer is if:
- There is no minor update for me (I'm at the latest point release) AND
- I've not clicked never for this major update version
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
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.