The Parallel process model sequences call the plug-in utility sequences, and the main Execution entry points in the Parallel process model use the following additional utility sequences:

  • Initialize TestSocket—The controlling execution calls the Initialize TestSocket sequence to initialize the data for and create the test socket executions.
  • Tile Execution Windows—The controlling execution calls the Tile Execution Windows sequence to tile the test socket Execution windows by building a list of executions and posting a UIMessage to the user interface that requests window tiling.
  • Monitor Threads—The ProcessDialogRequests sequence calls the Monitor Threads sequence periodically from the controlling execution to determine whether any of the test socket executions terminated or aborted. The Monitor Threads sequence updates the ModelData for terminated or aborted test sockets to indicate the new state and updates the UUT Information dialog box the controlling execution launches.
  • ProcessDialogRequests—The controlling execution calls the ProcessDialogRequests sequence from the Test UUTs sequence after displaying the UUT Information dialog box, which enqueues requests for sequence names into the ModelData.DialogRequestQueue parameter. The ProcessDialogRequests sequence loops while waiting for those requests. When the ProcessDialogRequests sequence receives a request, it calls the requested sequence. Additionally, the ProcessDialogRequests sequence periodically calls the Monitor Threads sequence to verify the state of and update the information for the test socket executions.
  • Run UUT Info Dialog—The controlling execution calls the Run UUT Info Dialog sequence from a new thread in the Test UUTs Execution entry point to initialize and launches the UUT Information dialog box the Test UUTs Execution entry point uses to display information and gather serial numbers for the test socket executions.
  • Continue TestSocket—The ProcessDialogRequests sequence calls the Continue TestSocket callback to notify the test socket to continue executing. The test socket execution waits on the notification in the default implementation of the PreUUT and PostUUT callbacks.
  • Terminate TestSocket—The ProcessDialogRequests sequence calls this dialog box request callback. The Terminate TestSocket sequence terminates the execution for the test socket the request specifies.
  • Abort TestSocket—The ProcessDialogRequests sequence calls this dialog box request callback. The Abort TestSocket sequence aborts the execution for the test socket the request specifies.
  • Restart TestSocket—The ProcessDialogRequests sequence calls this dialog box request callback. The Restart TestSocket sequence restarts the execution for the test socket the request specifies and re-tiles the Execution windows to include the Execution window the Restart TestSocket sequence restarts.
  • Terminate All TestSockets—The ProcessDialogRequests sequence calls this dialog box request callback. The Terminate All TestSockets sequence terminates all the test socket executions.
  • Abort All TestSockets—The ProcessDialogRequests sequence calls this dialog box request callback. The Abort All TestSockets sequence aborts all the test socket executions.
  • Stop All TestSockets—The ProcessDialogRequests sequence calls this dialog box request callback. The Stop All TestSockets sequence sets a flag for each test socket execution to stop after completing the current UUT test sequence. The sequence also sets a notification for test socket executions to continue to that point without interruption.
  • View TestSocket Report—The ProcessDialogRequests sequence calls this dialog box request callback to enable the View Report button in the UUT Information dialog box. Click the View Report button to launch a report viewer for the report file for the test socket the request specifies.
  • View TestSocket Report – Current Only—The ProcessDialogRequests sequence calls this dialog box request callback to enable the View Report button in the UUT Information dialog box. Click the View Report button to launch a report viewer for the last report generated for the test socket the request specifies. This sequence differs from the View TestSocket Report sequence in that it shows only the last report instead of the whole report file.