4.  XmString Tests

This README describes the OSF/Motif XmString and XmFontList
tests.  It provides information about the individual tests,
and offers instructions for running and interpreting the
tests and test output.

                            Note

Throughout this README, we use the path ./tests/XmString to
identify the top directory of the XmString tests.  The ./
indicates the testing tree root and is not an actual path
designation.  For example, if you installed the Motif 1.1
release software at /source/Motif, then ./tests/XmString
translates to /source/Motif/tests/XmString at your site.

4.1  Overview and Directory Structure

The OSF/Motif XmString tests directory, ./tests/XmString,
consists of several files:

   * The files Imakefile, Makefile, and Makefile.hp are used
     to build the tests.

   * The file run_FontList is used to run all the XmFontList
     tests in series.  It also cats the output of the tests
     into the file FontList.out

   * The file run_String is used to run all the XmString
     tests in series.  It also cats the output of the tests
     into the file String.out

   * The file convenience.c contains the source code for
     convenience routines used by all the tests.

   * Files with the suffixes .c and .h are the source files
     for the tests.

This directory contains the following tests.

FontListA         Tests adding fonts to FontLists.

FontListC         Tests creating FontLists.

FontListF         Tests freeing FontLists.

StringComp        Tests XmString comparison operations.

StringCopy        Tests XmString copy operations.

StringEmpty       Tests operations on empty, or incomplete
                  XmStrings.


4.2  Compiling the Tests

All the tests must be compiled before you can run them.

   * If you used the global build process after installing
     the software, the tests should already be built.  We do
     not recommend building the tests with global build pro-
     cess because of the size of the test suite.  (This
     assumes that you did not move the test suite files
     prior to invoking the make commands.)

   * If you did not include the test suite files in your
     initial global build process, you can build the tests
     now using the make all command from the
     ./tests/XmString directory.

The compiled tests use a large amount of disk space.  You
may prefer to build each test separately if disk space is
limited at your site. You can build each test individually
using the make command for each test.  For example, to com-
pile the FontListF test, enter the command make FontListF in
the ./tests/XmString directory.

4.3  Running the XmString Tests

The tests in this section are noninteractive.  They run
without input from the user and print their results to the
standard output.

You can run the test in series using the run_FontList and
run_String scripts.  These scripts redirect the output of
the tests to the files FontList.out and String.out, respec-
tively.  The run_FontList script runs the tests FontListA,
FontListC, and FontListF.  The run_String script runs the
tests StringComp, StringCopy, and StringEmpty.

To run any of the tests individually simply enter the name
of the compiled test in the ./tests/XmString directory.
When the test has completed, a summary of the results is
displayed on the standard output.

BUGS SHOWN BY THESE TESTS


StringWidth
PIRS No.:      4841
XmStringWidth returns wrong value after concatenating a few
direction segments to an existing XmString.
Version found in:      1.2

 
ENDBUGS
