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

no edit summary
No edit summary
Line 1: Line 1:
The following is just an initial dump of information to be used for future documentation.
The following is just an initial dump of information to be used for future documentation.


= Heartbeat Emitter =
= Prep =
 
Things in this section should be done before a release has landed.
 
# Check for a functioning heartbeat emitter. Run one if unsure.
# 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 ==
* Generates traffic to keep Pulse connections from being automatically closed.
* Generates traffic to keep Pulse connections from being automatically closed.
* Must be running -somewhere- on the internet. Can be anywhere.
* Must be running -somewhere- on the internet. Can be anywhere.
* Fine to run more than one. If you're not sure, boot one.
* Fine to run more than one. If you're not sure, boot one.


== Usage ==
=== Usage ===


  ./heartbeat_emitter.py
  ./heartbeat_emitter.py


== Options/Behavior ==
=== Options/Behavior ===


No other requirements. It will print out local time every time a heartbeat is sent, so you can diagnose time of any server failures or freezes.
No other requirements. It will print out local time every time a heartbeat is sent, so you can diagnose time of any server failures or freezes.


= Release Listener =
== Release Listener ==
* Listens for a release request and automatically runs the correct script
* Listens for a release request and automatically runs the correct script
* Run one per platform. Make sure a heartbeat has been set up.
* Run one per platform. Make sure a heartbeat has been set up.


== Usage ==
=== Usage ===


  ./release_listener.py --help
  ./release_listener.py --help
Line 41: Line 50:


This runs a listener in the qa-foobar cluster, platform set to mac.
This runs a listener in the qa-foobar cluster, platform set to mac.
== Options/Behavior ==
=== Options/Behavior ===
* Internally, our clusters are the hostnames of the Mac Pro that groups the platform VMs.
* Internally, our clusters are the hostnames of the Mac Pro that groups the platform VMs.
* --update will redefine which test script is called for update requests. The default accomodates our internal systems.
* --update will redefine which test script is called for update requests. The default accomodates our internal systems.
* --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.
canmove, Confirmed users
2,041

edits