QA/Automation/Projects/Mozmill Shared Modules/On Demand Testing: Difference between revisions

QA/Automation/Projects/Mozmill Shared Modules/On Demand Testing (view source)

987 bytes added , 12 August 2011

no edit summary

canmove, Confirmed users

2,041

edits

@@ Line 61: / Line 61: @@
 The existing update test scripts consume the directory tree created by the staging script to perform the desired total test run.
+==The Process after Phase II==
+Phase I concentrates on improving the Phase I process in two ways:
+# We've introduced a cluster concept so that multiple test clusters can be run without interfering with each other.
+# The system now works with functional tests as well.
+We've also introduced a new component, a heartbeat emitter. This is a temporary workaround, because we found that rolling out Pulse listeners that receive only sporadic traffic causes their sockets to be closed out from under them. The heartbeat emitter is simply a traffic generator.
+==The Process after Phase III (In Progress)===
+Phase III will be improving Phase II in one primary way:
+# The system will be kicked off from a web front end rather than via command-line
+The primary gain here will be simplifying the process for those who aren't used to ssh and command-line tools. Our goal is to simplify the test run process to the point that a non-automation person can ramp up on how to do it within minutes.