opusbb_test_driver

Summary

This is the test driver for the C-interface to the OPUSBB package. The package provides access to the blackboard routines of the Opus Application Programmer's Interface (OAPI), and the test driver exercises those routines.

Description

The OPUSBB test driver exercises the routines in the C-interface to the OAPI. The test driver should be run in both interactive and pipeline mode for each regression test.

In interactive mode, many of the OPUSBB calls have no affect, since there is no blackboard used in this mode. The test driver still performs some valid tests, and should be run. See the Usage section for how to run in interactive mode.

In pipeline mode, the test driver creates its own events, triggers on them, creates and modifies OSF and PSTAT files, and eventually cleans everything up.

To run the pipeline version, start the opusbb process in your sample pipeline path.

The driver will run for a short time (< 20 seconds), then should appear "idle". View your sample pipeline path in the OMG and you should see entries for:

dataset status ------- -------- testosf1 b testosf2 dc

You can then HALT the opusbb process, and the PMG entry should disappear if there were no errors. It will appear as ABSENT if any errors were detected, and you can view the process log file to see what might have gone wrong.

Usage

opusbb_test_driver -p pathname phonydataset

Input

OPUS process resource file (picked up by default, no command argument needed).

A phony dataset name (any string value).

Output

If successful, the last message written should be "Test succeeded."

Resource File

A resource file is required for running opusbb_test_driver, but the user should NOT alter any values in this file. They are set up to be correct for the execution of the test driver.

Required Command-Line Arguments

path_file_name

An OPUS path file for a SAMPLE PIPELINE path. A sample pipeline path MUST be used, since the test driver makes reference to several pipeline stages which only exist in the sample pipeline.

phonydataset

To inform the test driver that you are running in interactive mode, and not pipeline mode, a "dataset name" must be passed as a command line argument. This name will not be used by the test driver, other than checking for its presence on the command line.

Examples

$ opusbb_test_driver -p g2f blurb

Runs the test driver in interactive mode for the path "g2f". The last message written should be "Test succeeded.".