User:Strife Onizuka/Projects/TestHost/Coordinator: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
<div style="float:right;">__TOC__</div> | <div style="float:right;">__TOC__</div> | ||
= | = Scripts = | ||
It was my thought to | It was my thought to combine the different types of slave scripts to reduce the number of scripts. | ||
= | == Interface Coordinator == | ||
== Interface | This script handles the bidirectional communication between the high level and the lower level interfaces. It's job is to interpret the commands sent from the user (from a specific Interface script) and relay them to the appropriate script. Likewise it must also send messages from low level interfaces to the user in an understandable fashion. | ||
<pre></pre> | <pre></pre> | ||
---- | |||
=== Email Interface Handler === | === Email Interface Handler === | ||
<div id="box" style="padding: 0.5em"> | <div id="box" style="padding: 0.5em"> | ||
<pre></pre> | <pre></pre> | ||
==== Email Slaves ==== | ==== Email Slaves ==== | ||
<div id="box" style="padding: 0.5em"> | <div id="box" style="padding: 0.5em"> | ||
| Line 31: | Line 31: | ||
</div></div> | </div></div> | ||
== State Handler == | == State Handler == | ||
This script keeps track of the scripts state and handles messages from the | This script keeps track of the scripts state and handles messages from the IC ([[#Interface Coordinator |Interface Coordinator ]]). If the command cannot be parsed at that time because the script is in the wrong state, then an error message is returned to the {{HoverText|IC|Interface Coordinator}}. In the event of a test start command being sent, it passes the load command on to the TT ([[#Test Tracker|Test Tracker]]). | ||
<pre></pre> | <pre></pre> | ||
=== Test Tracker === | === Test Tracker === | ||
<div id="box" style="padding: 0.5em"> | <div id="box" style="padding: 0.5em"> | ||
The Test Tracker keeps track of test names, groups and test keys. It receives the command to start a test from the State Handler and configures the Test Runner. | |||
<pre></pre> | <pre></pre> | ||
</div> | </div> | ||
=== Test Runner === | === Test Runner === | ||
<div id="box" style="padding: 0.5em"> | <div id="box" style="padding: 0.5em"> | ||
The test runner receives its configuration information from the Test Tracker and actualy starts the tests specified. As the test information is returned it stores information in the Test Log Slaves. | |||
<pre></pre> | <pre></pre> | ||
---- | ---- | ||
==== Test Log Slaves ==== | ==== Test Log Slaves ==== | ||
<div id="box" style="padding: 0.5em"> | <div id="box" style="padding: 0.5em"> | ||
A simple database for storing test logs. | |||
<pre></pre> | <pre></pre> | ||
</div></div> | </div></div> | ||
Revision as of 18:14, 5 March 2007
Scripts
It was my thought to combine the different types of slave scripts to reduce the number of scripts.
Interface Coordinator
This script handles the bidirectional communication between the high level and the lower level interfaces. It's job is to interpret the commands sent from the user (from a specific Interface script) and relay them to the appropriate script. Likewise it must also send messages from low level interfaces to the user in an understandable fashion.
Email Interface Handler
Email Slaves
HTTP Interface
XML-RPC Interface
Dialog Interface Handler
Dialog Box Slaves
State Handler
This script keeps track of the scripts state and handles messages from the IC (Interface Coordinator ). If the command cannot be parsed at that time because the script is in the wrong state, then an error message is returned to the IC. In the event of a test start command being sent, it passes the load command on to the TT (Test Tracker).
Test Tracker
The Test Tracker keeps track of test names, groups and test keys. It receives the command to start a test from the State Handler and configures the Test Runner.
Test Runner
The test runner receives its configuration information from the Test Tracker and actualy starts the tests specified. As the test information is returned it stores information in the Test Log Slaves.
Test Log Slaves
A simple database for storing test logs.