DATE: 11/05/85

SECTION: TESTING REVISED: 11/06/87

SUBJECT: GENERAL INFORMATION

TESTING REPRESENTS A VERY CRITICAL PART OF SYSTEM DEVELOPMENT. IT IS OFTEN THIS PHASE THAT DETERMINES THE OVERALL PERFORMANCE OF A SYSTEM ONCE IT BECOMES A PRODUCTION JOB. IT IS THE POLICY OF THE COMPUTER SERVICES DIVISION THAT ALL PROGRAMS WILL BE FULLY TESTED BEFORE THEY GO INTO PRODUCTION OR BACK INTO PRODUCTION IF A CHANGE HAS BEEN MADE.

SINCE TESTING ALSO REQUIRES LARGE AMOUNTS OF BOTH PROGRAMMER AND COMPUTER TIME IT MUST BE DONE IN THE MOST EFFICIENT MANNER POSSIBLE. THIS HAS PROVEN TO BE REMOTE TESTING WITH THE PROGRAMMER NOT PRESENT. THIS PROCEDURE WILL BE FOLLOWED IN THIS INSTALLATION. ALL FUTURE DISCUSSIONS IN THIS CHAPTER WILL BE BASED ON THIS METHOD.

CHAPTER: PROGRAMMING NUMBER: 5.4.02.01

DATE: 11/05/85

SECTION: TESTING REVISED: 11/06/87

SUBJECT: TESTING PRIORITY

ALL TESTS WILL BE LOADED INTO THE SYSTEM ON A DATE AND TIME ENTERED BASIS. THE RESOURCES USED BY THE SYSTEM WILL DICTATE TO A LARGE EXTENT THE ORDER IN WHICH THE TESTS ARE COMPLETED. IN ALL CASES, THE TESTS WILL BE COMPLETED AS SOON AS POSSIBLE.

PRIORITY MAY BE OBTAINED FOR TESTING BY CONTACTING THE OPERATIONS SUPERVISOR AT LEAST ONE DAY PRIOR TO THE TEST BEING READY. THESE REQUESTS SHOULD BE ON AN EXCEPTION BASIS AND KEPT TO A MINIMUM.

CHAPTER: PROGRAMMING NUMBER: 5.4.03.01

DATE: 11/05/85

SECTION: TESTING REVISED: 11/06/87

SUBJECT: TEST REQUIREMENTS

TO INSURE ACCURACY IN PROGRAMMING THERE ARE CERTAIN BASIC TEST REQUIREMENTS THAT MUST BE MET. THESE ARE AS FOLLOWS:

1. ALL PROGRAMS MUST BE TESTED BEFORE BEING SUBMITTED TO STANDARDS AND PROCEDURES. THIS INCLUDES CHANGES TO EXISTING PROGRAMS AS WELL AS NEW ONES.

2. THE AMOUNT OF TEST DATA TO BE CONSTRUCTED SHALL BE DETERMINED BY THE COMPLEXITY OF THE PROGRAM. IT MUST BE SMALL ENOUGH THAT ALL OUTPUT CAN BE EXAMINED TO INSURE THAT THE PROGRAM IS PERFORMING PROPERLY.

3. THE TEST DATA SHALL BE CONSTRUCTED TO TEST ALL CONDITIONS WHICH MAY OCCUR. THE USE OF NORMAL PRODUCTION DATA WILL NOT USUALLY DO THIS.

4. VOLUME TESTS AGAINST LIVE DATA ARE TO BE MADE ONLY AFTER PROGRAMS HAVE BEEN SUCCESSFULLY TESTED USING SMALL VOLUME MODELS.

5. THE PROGRAM AREA SUPERVISOR MUST INDICATE THAT THE JOB MEETS THE SPECIFICATIONS AND REQUIREMENTS OF THE APPLICATION.

CHAPTER: PROGRAMMING NUMBER: 5.4.04.01

DATE: 11/05/85

SECTION: TESTING REVISED: 11/06/87

SUBJECT: USE OF FORMAT LIBRARIES

THE FOLLOWING GUIDELINES GOVERN THE USE OF IMS FORMAT LIBRARIES IN CONJUNCTION WITH ONLINE PROGRAMMING AND THE MESSAGE FORMAT SERVICES (MFS).

TWO CATALOGUED PROCEDURES EXIST FOR COMPILING SCREEN FORMATS. THEY ARE MFSBTCH1 AND MFSTEST. NEW SCREEN FORMATS CAN BE COMPILED FOR TEST AND PRODUCTION USE BY EXECUTING MFSBTCH1. THESE SCREEN FORMATS WILL ALWAYS END IN AN 'O1' (OH-ONE NOT ZERO-ONE). (REFER TO _E_&L0H_&A8L 2.3.07.01 OF THIS MANUAL FOR ADDITIONAL NAMING CONVENTIONS). THE MFSBTCH1 PROCEDURE WILL PUT THE SCREEN FORMAT ON LIBRARY IMSVS.FORMAT.

CHANGES TO EXISTING PRODUCTION SCREENS ARE ACCOMPLISHED BY COMPILING THE REVISED FORMAT UNDER THE MFSTEST PROCEDURE. THE MFSTEST PROCEDURE PUTS A TEST VERSION OF THE SCREEN ON THE IMSVS.TFORMAT LIBRARY. TO TEST THE CHANGES, THE PHYSICAL TERMINAL MUST BE SET TO TEST MODE BY ENTERING THE COMMAND /TEST MFS. THE TERMINAL WILL NEED TO BE RESET AFTER EACH TESTING BY ENTERING /END COMMAND. WHEN THE REVISED SCREEN FORMAT HAS BEEN COMPLETELY TESTED, RECOMPILE THE FORMAT USING MFSBTCH1. THE TEST MEMBER SHOULD SUBSEQUENTLY BE DELETED FROM IMSVS.TFORMAT WHEN TESTING HAS BEEN COMPLETED (I.E., WHEN THE CHANGED SCREEN HAS BEEN RECOMPILED USING MFSBTCH1).

CHAPTER: PROGRAMMING NUMBER: 5.4.05.01

DATE: 11/05/85

SECTION: TESTING REVISED: 11/06/87

SUBJECT: IMS TEST PROCEDURES

ALL IMS JOBS WILL BE THOROUGHLY TESTED USING TEST DATA BASES. THE FOLLOWING TEST PROCEDURES ARE TO BE FOLLOWED.

TEST DATA BASE WILL BE CREATED THAT CONTAIN ALL OR A PORTION OF THE RECORDS OF AN ACTUAL DATA BASE. THE IDENTIFICATION NUMBERS FOR DATA BASES, DATA BASE DD NAMES, AND DATA BASE DATA SET NAMES WOULD BE IDENTICAL TO THOSE USED FOR THE PRODUCTION DATA BASES WITH ONE EXCEPTION. THIS EXCEPTION WOULD BE THE SUBSTITUTION OF THE LETTER 'T' FOR THE LETTER 'D' IN THE 4TH POSITION OF THE IDENTIFICATION NUMBERS MENTIONED ABOVE. ALL DATA BASE IDENTIFICATION NUMBERS WILL BE REQUESTED THROUGH THE STANDARDS DEPARTMENT.

PROGRAM SPECIFICATION BLOCK (PSB) NUMBERS FOR ALL TEST TRANSACTIONS WILL BE REQUESTED THROUGH THE IMS AREA COORDINATORS. ONLINE TEST APPLICATIONS WILL HAVE PSB NUMBERS IDENTICAL TO THE PROGRAM IDENTIFICATION WITH THE EXCEPTION OF A 'C' IN THE 8TH POSITION DESIGNATING TEST. BMP AND BATCH JOBS WILL HAVE PSB NAMES ASSIGNED BY THE AREA COORDINATORS FROM THEIR AVAILABLE POOL OF TEST PSB NAMES. WHEN TESTING IS COMPLETE BATCH, BMP, AND ONLINE APPLICATIONS WILL USE PRODUCTION PSB NAMES, AND SUCH NAMES WILL BE IDENTICAL TO THE PROGRAM IDENTIFICATION.

CARE OF TEST DATA BASES ARE THE PROGRAMMER'S RESPONSIBILITY, AND CAUTION MUST BE EXERCISED TO INSURE THAT TEST DATA BASES DEFINED AS PART OF THE ONLINE IMS SYSTEM REMAIN CATALOGUED. THEIR ABSENCE WOULD PREVENT THE SUCCESSFUL INITIATION OF THE ONLINE SYSTEM.