CIS Unit Test Checklist

Owner Name: [Tim Sheehy]	Date: [22 Feb 2012]
Program(s): [CCN25R]	Transaction Name: [CABNOT]
Application: CIS	Subsystem: [Client Notices]
Bundle #: [ ]	Release: [16.6]
Tag #: [R033]	Version #: [ ]

Checklist – Section A	Developer	Team Lead / Reviewer
Program Standards	Yes	No	N/A	Yes	No	N/A
Are you using the version of code checked out of Workbench and confirm that nobody else is working with the same program?
Does the code adhere to the Application Development Standards as established by the Commonwealth and the Project?
Has Revision History Log been updated?
Does the appropriate tag appear on all new and changed lines of code?
Is the environment-specific coding implemented?
Has the program profile in Work Bench been verified (compile Options, DMS, RDMS, Keywords, etc.)?
Does the code use the online/batch skeleton?
Are variable declarations properly named & commented?
Are complex algorithms and optimizations adequately commented?
Dependencies	Yes	No	N/A	Yes	No	N/A
Has the impact to other interfacing applications (Data Warehouse, COMPASS Portal, etc.) been determined?
Have table updates (Ref tables etc) been checked (especially TTXN, TZZZ, TMSG)?
Has the impact been assessed on other components that could be affected by this changes (procs, subroutines, screens)?
Do calls to any other programs use the appropriate number and size of parameters?
Have the traveler dependent pre/post programs been updated (batch only)?
Performance	Yes	No	N/A	Yes	No	N/A
Has the impact to database inputs and outputs been identified?
Has the impact to Common Storage been determined?
Does the code have a significant / measurable impact on size and/or memory use?
Online Programs	Yes	No	N/A	Yes	No	N/A
Have the screen layouts been updated and verified against approved screen mockup?
Is the Function key one table updated?
Corresponding online menu(s) updated?
Have the standard error numbers been obtained / used for common edits?
Have edit numbers been obtained for all screen specific edits? Have they been updated in the specification document?
Batch Programs	Yes	No	N/A	Yes	No	N/A
Has the Job Documentation Form been completed for new/existing programs?
Have Travelers been created for the new programs and revised for the modified programs?
Have the Stringers and Op-Cons procedures been initiated for all components?
Has switch 23/24 been used during coding to address abnormal termination?
Is the program coded to update the BCF counts for the files?
Are proper DISPLAY statements and process summaries created by the new components?
Are new ECLs created using the appropriate Pack-Ids for the respective environments?
Have the changes been scheduled?
Has new or modified inputs and/or outputs been included (also ECLs)?
Unit Test (Common)	Yes	No	N/A	Yes	No	N/A
Are all the software components in place to complete unit test?
Has the program been tested in Web TS on-line?
Did you test to break? (i.e. not only your changes)?
Were the CATIPR and TIP$ checked?
Have the results been documented?
Have the CONVER DUMP1, CONVE2 been analyzed?
Have the Input, Output and Reports for counts and formats been verified?
Unit Test (On-line only)	Yes	No	N/A	Yes	No	N/A
Initial cursor position verified?
Are the applicable function keys tested (specifically F1, F3, F5, F8, F13)?
Did the test start with a blank screen?
Was the transaction tested in the queue?
Did the navigation test flow (next appropriate transaction came up correctly)?
Has the testing been conducted in all modes?
Did the navigation test flow?
Unit Test (Batch only)	Yes	No	N/A	Yes	No	N/A
Switch 23/24 tested?
Was the job executed in a run stream?
Were the travelers executed?
Migration Check	Yes	No	N/A	Yes	No	N/A
Is the program checked back into the Workbench?
Have the breakpoints been removed prior to migration?
Has the unnecessary code been deleted (not commented)?
Has migration request form been filled out completely and accurately??
Has the compile sequence been specified along with the migration request?
Has the appropriate team lead been notified that the program is ready?
Is there any follow up action required? If so, explain:
Was a code review conducted ?
Was a DOWN performed and analyzed? (against which version - e.g. PROD*BQA-SYM v 36)

Changes made / Comments – Section B

Unit Test Scenarios – Section C
Test Scenario (Team Lead/Reviewer)	Expected Results (Team Lead)	Actual Results (Attach)	Pass?
See below	See below	See below

Sign Off

[Timothy Sheehy]	[02/22/2012]

Developer	Date

[Kranthi Dasi]	[02/22/2012]

Code Reviewer	Date

[Doug McHenry]	[02/22/2012]

Team Lead / UTC Reviewer	Date