All receivers should be started before any events are sent in to the correlator and set to write events to file. The file(s) can be easily compared to reference output using standard operating system tools.

Other tools are also useful in checking the output. The engine_inspect correlator utility is good for verifying that the right number of monitor instances and listeners is present after (stages of) a test. Also, you can use this utility to detect listeners and monitor instances that never terminate, or premature existence of monitor instances.

Use the engine_receive utility to capture event output. You can specify the -f option to pipe received events to a file. Start multiple receivers on different channels as required

The engine_inspect utility provides useful data for testing including the number of monitor instances, listeners, receivers, events generated and so on. Split input event files and run the engine_inspect utility after each file.

Capture the correlator log and compare to reference data. This is useful if your application logs errors or there are interesting diagnostics.