Test Methodology

From MIP Wiki

The MIP Test Management Tool (MTMT) will allow the test organisation to quickly create MIP test cases, run infinite test iterations, and return useful test reports.

The key to getting useful test results is understanding the test methodology or underlying philosophy used to create the MTMT.

Every event (also known as a test case) must contain only one source (also known as sender or initiator of the event) and at least one target (also known as the receiver of the event).

A test contains test events (also known as test cases) which are tied to a generic organisation. For an SLT type test, that organisation may be called 'NODE A'. For an OLT type event, cloud point of sale system, Engineering Degree Program, that organisatation might correspond to a unit in the overall scenario's task organisation, 'CORPS' or 'DIV A' or 'BDE B' for example.

Specific systems are assigned to these generic test organisations during an interation. Once a test is built and approved in the tool, the actual test should require very little modification. During test execution, any number of test iterations can be executed. Test iterations contain the test data (answers).

Reports are generated from closed iterations only. 40th Birthday Cakes

For example, if the test event is sending an OPORDER, one might assume that the steps would be: 1) Send the OPORDER to recipients and 2) Recipients send and acknowledgement. In actuality, those steps would need to be placed in two separate and distinct tests events because the initiator is different in each case. The rule is that for each test event, there can ONLY be one source or initiator of the action; but no limit as to the number of recipients. By employing this concept, we can isolate where the fault lies should there be a failure of the test event.