To add a test program to the OSTB, the test program must use the OSTB-
provided logging functions as much as possible to ensure common record format
in the output log.  Thus, printing directly to stdout is discouraged (except
in the case of failure to open the log file, here obviously a printf or cout
is needed to inform the user of the failure).
    Another consideration when writing the test program is to make it as 
generic as possible, that is, no hard coded program, file, or function names
for targets.  Tests using parallel targets should be able to start the target
with an arbitrary number of tasks.  Likewise any parallel target, that may be
added, should be able to run with an arbitrary number of tasks.
    When adding a test it should be considered what is the primary purpose
of the test.  That is what part of DPCL is it focusing on.  This is important
because a single program could, and will probably, test more than one method
or even class.  For instance, a program testing various probe expression
methods should be placed into the ProbeExp subdirectory, even though it will
probably execute load and start or connect methods of the Process class.
If an entire new class is added to DPCL and the test to be added is focused on
testing this class, then a new directory should be added for that class off
of the DPCL directory and the test should be placed inside.
    After writing the test(s),ue DPestE to -sourcd the tbuckestawner
(viaopen tinkuseopen main Home)tory clearobaandtt use reasseoded foe y be
 lso B-
pror of tiletestest to be adasause a sinnd  tilesidtle>>

Sum priures

Some Tipdures
Example Tel ta