Script Execution

Once a selected script starts a status window and a log widow are displayed. The status window lists the specific functions that must be executed in order for the script to pass. On the left hand side of the functions is a placeholder to indicate pass/fail for each step. Generally the E5515C and MIP setup are the first functions performed. The log will show each bit of communications between the entities and the results. Once the setup is complete the "setup" function is marked as "pass". The script then begins the next step. If the user is required to perform a function on the device under test, a prompt window pops up directing the user to take an action. The prompt typically provides suggested methods such as the AT command that may be used to implement the action. The prompt may also ask the user to verify state or action of the device under test. The script proceeds through the steps until all have passed. If there is a failure, the script stops at that step. Generally it is up to the user to ensure the device under test is in the correct mode for the next test.

Once the script completes, the information in the status screen is added to the end of the log. if the "include_ppp_packets_in_log = True" in the config file, the ppp dump is obtained from the MIP-5850 and placed in the log file (after the standard log and before the status information). The entire log is then saved to disk. Note that the TCP dump can be enabled or disabled via the configuration database.

Note that the scripts poll the MIP-5850 to determine if a specific action has happen. if the MIP-5850 has not received the message, it returns ERROR as seen in the below log. This is expected behavior and does not indicate a problem. However, if it does not see the required message in an appropriate time, it should be considered a failure. Generally there are no time limits placed on a wait for a message if the message is initiated by user action.

The format for the file name is:

testnumber testname yyyymmddhhmmss.log