Automated Test Framework

Framework Overview

The MCS Automated Test Framework (ATF) defines the objects, process and structure for creating and distributing an MCS test specification(s), called a 'Satellite Work Order', to one or more remote MCS Satellites (What is a satellite?) that have been established throughout one or more networks. There are essentially four parts to the ATF process.

MCS Test Object (MTO)

An MCS Test Object establishes a container that defines:

• The test type(s) to be run, e.g. VoIP, Throughput, Route, Capacity, DNS, Firewall etc. (see Test Types)
• The parameters that govern each of the defined test types. For example the length of the test, packet size where applicable etc. (See Test Options)
• The test(s) sequence order, namely 1st, 2nd, 3rd
• The test concurrency, namely run ‘with’ run ‘after’

MCS Satellite Work Order (SWO)

An MCS Satellite Work Order establishes a container the defines:

• The Test Object(s) to be processed
• The order of Test Object(s)
• The time cycle of the Test Object(s)
• The number of Test Object iterations including continuous
• The concurrency of Test Objects
• The Test Object destination target (satellite) for the test
• The reporting destination target if more than one database is supported

MCS Work Order Assignment

The process of assigning a Satellite Work Order establishes:

• The number of the MCS Satellites that will initiate and manage the individual MTO specifications
• The locations and therefore origination point(s) of presence (OPOPs) for MTO specifications

MCS Work Order Assignment

The process of assigning a Satellite Work Order establishes:

• The number of the MCS Satellites that will initiate and manage the individual MTO specifications
• The locations and therefore origination point(s) of presence (OPOPs) for MTO specifications