test.doc (c)Copyright Sequiter Software Inc., 1992-1993.
      All rights reserved.
      
      ---------------------------------------------------------------
      
           CODEBASE 5.0 TEST CODE INFORMATION
      
      I.   Files Provided for Test Code Use
      
      II.  General Testing Information

      III. Testing With CodeBase 5.0 Multi-Platform Version
      
      ----------------------------------------------------------------
      
      I.   Files Provided for Test Code Use
      
      Files provided for Testing are:
      
      T4MAIN.C         Main module.  Calls test source code modules
                       listed below.

      T4TEST.C         Test output display module.  

      T4TEST.H         Include file needed for 'T4TEST.C', which provides 
                       Windows and DOS screen I/O.

      T4BCD.C          Test source code modules.  Link any one of these
      T4CONV.C         modules with T4MAIN.C and T4TEST.C to create
      T4DATA.C         a DOS or Windows executable test program.
      T4EXPR.C
      T4GROUP.C
      T4INDEX.C
      T4INDEX2.C
      T4INDEX3.C
      T4INDEX4.C
      T4INDEX5.C
      T4LARGE.C
      T4MAX.C
      T4MEMO.C
      T4OPT.C
      T4PACK_Z.C
      T4POSITI.C
      T4SEEK.C
      T4SKIP.C
      T4SORT.C
      T4SORT2.C
      T4UNIQUE.C
      T4UNIQ2.C
      T4WRITE.C
      T4WRITE2.C
      T4WRITE3.C


      T4BOR.BAT        Batch file to test using Borland C++ 2.0 and up.
      
      T4WATCOM.BAT     Batch file to test using Watcom C 386 w/ Ergo
                       DOS extender.   Versions 8.5 and up.

      T4META.BAT       Batch file to test using Metaware High C 3.0 
                       w/ Phar Lap 386 DOS extender.
      
      T4MSC.BAT        Batch file to test using Microsoft C 6.00b and up.
      
      T4ZOR.BAT        Batch file to test using Zortech C++ 3.0.
      
      T4TCPP.BAT       Batch file to test using Borland Turbo C++ 1.01 and up.

      T4BORWIN.BAT     Batch file to test using Borland Turbo C++ under
                       Windows. 

      T4MSCWIN.BAT     Batch file to test using Microsoft C under
                       Windows.  

      T4IBMC.BAT       Command file to test using IBM C SET/2 under OS2 2.0

      T4WATCOM.CMD     Command file to test using Watcom C 386 under OS2 2.0

      ---------------------------------------------------------------
      
      II.  General Testing Information
      
         The test code can be used uder DOS, OS2 (command line) or 
      Windows.

         To test, make sure compiled library and test code source and
      headers are present on the current subdirectory.  Then execute
      appropriate  batch file.  Batch file will compile test code and
      automatically run it as well.
      
         When creating test code to run under Windows using T4MSCWIN.BAT
      or T4BORWIN.BAT, the Windows executables are not automatically run.
      Created Windows executables are named according to the 'Test source
      code modules' (see above).  They can be run individually under 
      Windows by using the Windows 'RUN' command.

         'T4MUL' and 'T4MUL2' tests multi-user capabilities.  These can
      be run as a DOS application on a network, as a Windows application,
      or as an OS2 command line application.

         If you are using a compiler or version of a compiler that is not
      officially supported by CodeBase but want to use CodeBase on that
      system, the test code should be used first to determine
      correctness.  If the test code compiles and runs successfully, it
      can be safely assumed that CodeBase will work correctly

      ---------------------------------------------------------------


      III. Testing With CodeBase 5.0 Multi-Platform Version

      The provided script file, 'diag' will compile, link and run the 
      test code on UNIX systems.  The tests used are the same as the
      tests used in DOS.

      NOTE:  Some of the tests use extremely large records, fields and 
      other attributes during testing.  Therefore, some tests that may
      fail should not cause undo concern for the vast majority of 
      applications written.  Contact Sequiter Software with any 
      concerns.

      Macintosh users should add T4MAIN.C and T4TEST.C, and any one of 
      the test code source modules, listed above.

      Compilers that do not easily support command line parameters when
      executing programs should set the define S4NO_PARMS.  This will
      enable a default set of parameters when executing the test modules.
      This switch is pre-defined when using the Macintosh.

            -------------------  END  ---------------------