EDSBack v1.12 BETA
                   Copyright (c) 1994 by Eric D. Scales

                    T E S T I N G   O B J E C T I V E S
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

NOTE:  If you see something that you would like changed or added, please feel 
       free to notify Eric Scales on the change.  If it is a reasonable 
       request it will be added.
 
 
 - Try calling remotely to make sure the screen output the user sees is 
   the same as what you see..
 
 - Read through the entire documentation.
     -Make reports to the author on grammatical and spelling errors.
     -Make reports on subjects that are unclear or too broad.
     -Make reports on parts of the document that should be deleted.
 
 - Make sure EDSBack is dialing according to the dialing templates..
     -Make sure EDSBack dials the proper numbers..  (Check your log and look
      at the EDSBack DialString and make sure it was correct)
     -Make sure EDSBack is properly finding the numbers it is allowed to 
      call.

 - Make sure EDSBack is properly importing text files into their respective
   databases.

 - Make sure the index files operate properly..  Periodically check your
   log for the line (EDSBack Performance) and report to me any instances 
   where EDSBack scanned more than 25 times.

 - Fully test the communications routines.
     -Make sure EDSBack recognizes modem result codes properly.
     -Make sure EDSBack recognizes when the modems are connected.
     -Make sure EDSBack does not get caught in a "forever" loop.
 
 - Fully test the already used number trash can file builder.
     -Make sure it ONLY adds numbers that have 10 numbers in them.
     -Make sure it properly updates the trash file.
     -Make sure it writes an accurate log.
     -Make sure it is searching for the correct users.
 
 -Fully test the upgrading facility
     -Make sure EDSBack upgrades the security levels according to that set
      in the config file.
     -Make sure EDSBack upgrades to the proper expiration date.
     -Make sure EDSBack upgrades the proper Expired security level.
     -Make sure EDSBack is correctly addressing messages.
     -Make sure the values are actually saved to the user record.
     -Make sure the EDSBack comments are added to the place specified in the
      config file. (UNOTE1, CMNT1, etc.)
     -Make sure EDSBack is not writing the same number twice in the TRASH.BIN
      file
 
 -Fully test the International support
     -Make sure EDSBack is correctly dialing the number.
     -Make sure EDSBack waits long enough for a connection.
 
 -Fully test the delays
     -Make sure EDSBack allows callers of all speeds enough time to connect.
      (2400 usually takes longer to negotiate)
 
 -Fully test the verification prompts
     -Make sure the user has to enter the correct information for EDSBack to
      accept it.
     -Make sure the user isn't denied access for correct information being
      entered.
 
 -Look Closely at the Prompts when EDSBack runs.
     -Make sure no color "bleeding" takes place.
     -Make sure the prompts are precise and to the point.
     -Make sure the prompts are correct for the operation taking place.



 Thanks for taking the time to test EDSBack.   This file should be updated
 regularly during updates.  When a bug is found, please call E.D.S. 
 Development (Number is in the EDSBACK.DOC file) and enter your message to 
 Eric Scales in the EDSBack conference.  Same goes for wishes for 
 changes/additions to EDSBack/EDSUtil.