QA/Mozmill Test Automation/On Demand Update Testing/Documentation: Difference between revisions

no edit summary
No edit summary
Line 1: Line 1:
= Prep =
= System Prep =


Things in this section should be done before a release has landed.
Things in this section should be done to configure the system.


# Check for a functioning heartbeat emitter. Run one if unsure.
# Check for a functioning heartbeat emitter. Run one if unsure.
# Set up listeners on all desired platforms, grouped with a common cluster name.
# Set up listeners on all desired platforms, grouped with a common cluster name.
# Create a configuration file for release staging.
# If update testing, pre-stage the release.


== Heartbeat Emitter ==
== Heartbeat Emitter ==
Line 54: Line 52:
* --functional will redefine which test script is called for functional requests. Again, the default accomodates our internal systems.
* --functional will redefine which test script is called for functional requests. Again, the default accomodates our internal systems.
* --debug lets you know when things are ignored due to platform/cluster mismatches. This can be very noisy, but it's useful when you have no idea why something isn't responding.
* --debug lets you know when things are ignored due to platform/cluster mismatches. This can be very noisy, but it's useful when you have no idea why something isn't responding.
= Release Prep =
The things in this section should be done on a per-release basis, prior to the release.
# Create a configuration file for release staging.
# If update testing, pre-stage the release.
== Configuration File ==
=== Sample File ===
; Example configuration for an update test-run
[testrun]
; Application to test
application=firefox
; Type of test, could be update or bft
script=update
; Destination folder builds will be saved to
directory=3.6.20
; One section per platform tests are being run on:
;
; Section name is the specific OS, one of:
;  win2000, winxp, vista, win7, win7_64, linux, linux_64, mac
;
; platform key refers to the binary's platform in the filename, one of:
;  linux, linux64, mac, mac64, win32, win64
;
; Rest of keys are test matrix for that OS, as:
;  version=locale1 locale2 locale3
[win7]
platform=win32
3.6.18=en-US de
3.6=en-US fi
[winxp]
platform=win32
3.6.18=en-US fr
3.6=en-US it
[mac]
platform=mac
3.6.19=en-US de
3.6.18=en-US ja-JP-mac
3.6=en-US fr
[linux]
platform=linux
3.6.18=en-US pl
3.6=en-US en-GB
=== Usage ===
Create the file as in template above. Do note the difference between the OS specifiers and the binary platform specifiers, particularly linux_64 vs. linux64.
The OS specifiers must correspond to the "platform" given as a command-line parameter when launching the release listeners, above. The ones given as possibilities in the example above are the ones we use for our release listeners.
canmove, Confirmed users
2,041

edits