3,035
edits
No edit summary |
|||
| Line 2: | Line 2: | ||
To learn a little about what logic determines what XML is displayed, see the [http://people.mozilla.org/~morgamic/aus-partner.jpg AUS flow chart]. | To learn a little about what logic determines what XML is displayed, see the [http://people.mozilla.org/~morgamic/aus-partner.jpg AUS flow chart]. | ||
= Test | = Test Assumptions = | ||
Sets of rules we can use to make our tests easier: | 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 | * 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. | * One-off buildID offerings will have an added partial update that points to the latest build. | ||
= The General Plan = | = The General Plan = | ||
| Line 12: | Line 12: | ||
* Generate CLI script to show pass/fail status of new changes pre-release | * Generate CLI script to show pass/fail status of new changes pre-release | ||
Scope | = Scope = | ||
* Start small -- start by only testing release channels | * Start small -- start by only testing release channels | ||
* Branch into release and fallback scenarios | * Branch into release and fallback scenarios | ||
* Delve into nightly testing as time allows (bigger job) | * Delve into nightly testing as time allows (bigger job) | ||
= Existing Tools = | = Existing Tools = | ||
edits