/*<pre><b>
/ Program name : fit(progname.sas)
/ Program being validated as fit-for-purpose : (progname.sas)
/ Template design date : 16-Aug-2007 (do not change this date)
/=========================== FIT-FOR-PURPOSE VALIDATION ========================
/ Notes : This member is for documenting the "fit-for-purpose" validation of a
/         sas program, macro or a collection of programs or macros where
/         "triple test pack" validation is not appropriate. It is aimed at
/         more complex programs or macros or those that run processes rather
/         than process data. This is a lower level of testing than "triple test
/         pack" validation so any calculated results (if any) are not deemed
/         to be validated and will have to be validated by another means such as
/         double programming. The user can run test code in this member if
/         desired. If you intend to run test code then you should ensure that
/         the sasautos=() statement at the start of the code explicitly points
/         to the macro library whose macros are being tested with no other macro
/         libraries assigned to the sasautos declaration.
/========================= Program author documentation ========================
/ Program author :
/ Notes in this section read : No
/ Online document(s) that describe(s) program purpose : 
/ Online document(s) that describe(s) program features :
/ Online document(s) that describe(s) program output (if any) :
/ User has permission to make and keep copies of the above documents : No
/ Author validation date : dd-mmm-yyyy
/ Notes : All the relevent online documents should be listed. The users will
/         be expected to make copies of these documents and store them locally
/         in electronic form so the author has to grant permission for this. The
/         same document might fall into more than one of the above categories
/         but should still be repeated.
/         A validation date entered indicates that the documentation in this
/         section is complete. This should only be filled in if all the fields
/         in this section have been entered and there are no "No" answers in
/         this section.
/====================== User fit-for-purpose documentation =====================
/ Checker :
/ Notes in this section read : No
/ Copies of all the documents listed in the author section stored locally : No
/ Copy of online document(s) that describes program purpose : 
/ Copy of online document(s) that describes program features :
/ Copy of online document(s) that describes program output (if any) :
/ User requirements specification document :
/ Document authorizing use of the program :
/ Code tests added by user : 0
/ Code tests OK : N/A
/ User validation date : dd-mmm-yyyy
/ Notes : The copies of the online documents should match one-to-one with the
/         list provided by the author for easy identification except that these
/         copies should be stored locally in a safe place.
/         If no user requirements specification document exists then this should
/         be the document where it is agreed that the program features as
/         described by the author meet the user requirements.
/         The user can run test code in this member if desired, in which case
/         the sas log should be kept.
/         A validation date entered indicates that the documentation in this
/         section is complete. This should only be filled in if all the fields
/         in this section have been entered and there are no "No" answers in
/         this section. This should be stored in a safe place with read-only
/         permissions as proof of fit-for-purpose validation done.
/===============================================================================
/ AMENDMENT HISTORY:
/ init --date-- mod-id ----------------------description------------------------
/ 
/=============================================================================*/

*- sasautos should point to the macro library under test and no others -;
options sasautos=("explicit-path-name-of-macro-library");


************************ (optional) user testing start ************************;

************************* (optional) user testing end *************************;


***************************** END OF TEST PROGRAM *****************************;