1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/testing/release/README.txt Wed Dec 31 06:09:35 2014 +0100
1.3 @@ -0,0 +1,63 @@
1.4 +Mozilla Build Verification Scripts
1.5 +---
1.6 +
1.7 +--
1.8 +Contents
1.9 +--
1.10 +
1.11 +updates -> AUS and update verification
1.12 +l10n -> l10n vs. en-US verification
1.13 +common -> useful utility scripts
1.14 +
1.15 +--
1.16 +Update verification
1.17 +--
1.18 +
1.19 +verify.sh
1.20 + does a low-level check of all advertised MAR files. Expects to have a
1.21 + file named all-locales, but does not (yet) handle platform exceptions, so
1.22 + these should be removed from the locales file.
1.23 +
1.24 + prints errors on both STDOUT and STDIN, the intention is to run the
1.25 + script with STDOUT redirected to an output log. If there is not output
1.26 + on the console and an exit code of 0 then all tests pass; otherwise one
1.27 + or more tests failed.
1.28 +
1.29 + Does the following:
1.30 +
1.31 + 1) download update.xml from AUS for a particular release
1.32 + 2) download the partial and full mar advertised
1.33 + 3) check that the partial and full match the advertised size and sha1sum
1.34 + 4) downloads the latest release, and an older release
1.35 + 5) applies MAR to the older release, and compares the two releases.
1.36 +
1.37 + Step 5 is repeated for both the complete and partial MAR.
1.38 +
1.39 + Expects to have an updates.cfg file, describing all releases to try updating
1.40 + from.
1.41 +
1.42 +-
1.43 +Valid Platforms for AUS
1.44 +-
1.45 +Linux_x86-gcc3
1.46 +Darwin_Universal-gcc3
1.47 +Linux_x86-gcc3
1.48 +WINNT_x86-msvc
1.49 +Darwin_ppc-gcc3
1.50 +
1.51 +--
1.52 +l10n verification
1.53 +--
1.54 +
1.55 +verify_l10n.sh
1.56 + unpacks an en-US build for a particular release/platform, and
1.57 + then unpacks and compares all locales for that particular release/platform.
1.58 +
1.59 + Expects to have a file named all-locales, but does not (yet) handle platform
1.60 + exceptions, so these should be removed from the locales file.
1.61 +
1.62 + Best practice is to take a directory full of diffs for a particular release
1.63 + and compare to a directory full of diffs for the current release, to see
1.64 + what l10n changes have occurred. For maintenance releases, this should
1.65 + be slim to none.
1.66 +
