User:Strife Onizuka/Projects/TestHost/Coordinator

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.

Because there are multiple interfaces I've listed priorities for completion. Optional interfaces may or may not get implemented but are included as a place holder.

---

Chat Interface - Input/Output

Priority: 10 - Required by Spec

Email Interface Handler - Input/Output

Priority: 9 - Required by Spec

Email Slaves

HTTP Interface - Output

Priority: 7 - Required by Spec

Dialog Interface Handler - Input/Output

Priority: 5 - Optional

---

Dialog Box Slaves

XML-RPC Interface

Priority: 1 - Optional

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.

list groups;
list uuids;
list tests; //[integer group_index, string name, integer inv_uuid_index]

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.