Testing programs

Optionally, you can test your program using a proof list to ensure that it is running as you expect.

You can test all supported starting events, or a subset of events to test a specific program flow.

Note: Test programs are not supported with SQL views or audiences in start stages.

The test sends messages to your proof list, shows which paths ran, and the number of enactments that ran through each path.

Unsupported events

Currently, the following events are not supported for testing:

  • Cart abandon
  • Browse abandon
  • Purchase
  • Connect
  • SMS Campaigns through an event switch

  • Email notifications when selections are made in a performance switch or stage gate

  • Form submissions and Web services through a custom event

Before you begin

Before testing a program, you need to:

  • Create a seed group for your list
    This group will be used as the seed list that receives test messages. For information about creating a seed group, see Creating proof/seed group lists.
  • Validate the program to ensure that it is constructed correctly
    When you test a program, Program validates it automatically. You can also validate a program from the Design tab while designing it; this way, you will not have to return to the Design tab to fix errors. To manually validate a program, click Validate in the Design tab.

If validation errors exist when you attempt to test the program, a message will notify you that all errors must be fixed before the program can be tested.

To open the Design tab and fix the errors, click Fix on the message. Objects with validation errors are highlighted on the canvas and the errors are listed in the right pane.

Click Validate as many times as needed until all errors are cleared.

Testing

To begin the test:

  1. Select the Test tab.
  2. To select a proof list, click Test settings, select the proof list, and click OK.
  3. Click Promote draft.

    Promoting a draft makes it available for testing.

    If the program is error free, it is ready to be tested. If the program contains errors, click Fix on the notification message, fix the errors, then repeat steps 1-3.

  4. Select the starting event and timer options as needed:
    • Events - selecting the event brings enactments into the test instead of using the event schedule. By default, all supported events are selected. Clear the check boxes of any events you do not want to include. You must select at least one starting event.
    • Timers - the Pass through mode passes entries through the timer immediately instead of using the timer settings. The Stop mode stops the enactments at the timer until you allow them to pass through. By default, all timers are in the Pass through mode.

      Tip: If you are waiting for behavioral data, use the Stop mode for the data to be collected.

  5. Click Test.

    The test starts running. The progress bar at the top of the page shows the test status:

    • Initiating—The time required to create entries via Scheduled Filter execution or to prepare for events.
    • Active—The test is either routing enactments and/or waiting for events to occur.
    • Stopping—The test is stopping.
    • Stopped—The test stopped.

    Progress is automatically refreshed every 30 seconds. To refresh manually, click Refresh.

  6. To end the test, click Stop.

    To re-test the same draft, for example a different flow, click Reset.

Learn more

Program, test, proof list, seed group, validate