Notification Test Example Explained (2 of 2)

This functionality is supported only if you are using the Classic Agent.

The code in this two-user notification test is much the same as the code in the single-user example, except that the test is distributed across two CcMail applications. Thus the primary differences in this example are in the program flow.

Note: The described actions are carried out sequentially rather than concurrently.

The following actions are carried out by the code in the two-user notification test:

Before the test starts

  1. The SetUpMachine function is carried out on two machines; the first machine defaults to the base state, but the second machine specifies an application state that ensures that its InBox is empty.
  2. The Username and Password values for both machines are set.
  3. The SetMultiAppStates function is invoked for both machines.
    Note: This function will set different application states for the two machines.

On Machine 1:

  1. The SetMachine function specifies that Machine 1 should receive the next operation.
  2. A simple message is sent to Machine 2.

On Machine 2:

  1. Verify that the Alert dialog box exists.
  2. Verify that the Alert dialog box is active. If it is not, the exception’s error message will be Verify ALERT failed....
  3. If the Alert dialog box has opened, dismiss it by clicking OK.
  4. Refresh the InBox by picking the Inbox choice from CcMail’s Window menu.
  5. Verify that the Message menu’s DeleteMessage menu item is enabled, proving that the message is in the Inbox. If Verify fails, which means the menu item is not enabled, the exception’s error message will read, Verify MESSAGE WAITING failed....