Code Review/Unit Test Checklist for WO - [xxxx]

Program ID/Version: [PROGRAM NAME/version #]	Date: [ mm/dd/yyyy]
Online Batch Common Routine
Developer Name: [ ]	Reviewer Name: [ ]
Package #: [ ]	Release: R[ ]

Required Checklist – Section A	Developers	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 COBOL Standards?
Standard literals (PACLITS, PACGAML) updated?
Have the standard error numbers been used for common edits?
Does the wording of new error message match those in the DSD?
Comments and Coding Conventions	Yes	No	N/A	Yes	No	N/A
Has Revision History Log been updated?
Does the work order number appear on all new and changed lines of code?
Are variable declarations properly named and commented?
Has the code been commented adequately?
Have the line numbers been resequenced?
Unit Test	Yes	No	N/A	Yes	No	N/A
Were all the software components in place to complete unit test?
If an online program, has the program been tested in TIP, demand and eQuate?
Did you regression test?
Did you produce/update the Unit testscript?
If corrections were made was the program retested?
Have results been documented?
Migration Check	Yes	No	N/A	Yes	No	N/A
Is the program checked back into the Workbench?
Has migration request form been filled out completely and accurately?
Was a DOWN performed and analyzed? (against which version: 245)
Have table updates (Ref tables etc) been made/checked?
File Layout Changes (G$LCP, LREC) included?
Entry Points have been included?
Database Schema ready to be installed?
If screen changes were required, have the necessary screens and procedures been included?

Optional Checklist – Section B	Developers	Team Lead/Reviewer
Report Changes N/A, 25 – 26 Required only for reports	Yes	No	N/A	Yes	No	N/A
If a printed report, does the report meet standards, including header information?
If an eReport, is the eReport development complete?
Batch Programs N/A, 27 -30 Required for reports & batch	Yes	No	N/A	Yes	No	N/A
Has the Job Documentation Form been completed for new/existing programs?
Have additions or modifications to the schedule been documented?
Have new or modified inputs and/or outputs been included?
Have new or modified CKPT/CKPA parameters been included?
ECL/Sort Modifications N/A, 31–34 Required if ECL are added/changed	Yes	No	N/A	Yes	No	N/A
New or modified ECL’s?
New or modified LOUIS dumps?
New Q-REF?
New or modified sorts?
Screen Changes N/A, 35-40 Required for Online screen changes	Yes	No	N/A	Yes	No	N/A
Have the screen layouts (WebTS/TIP) been updated and verified against approved screen mockup?
Have eQuate changes been requested and completed?
Initial cursor position verified?
Applicable function keys tested?
Did all drills navigate correctly?
Were all picklist values verified?
GAM and Form Changes N/A, 41-44 Required for GAM/Form Changes	Yes	No	N/A	Yes	No	N/A
GAM table changes completed?
GAM Program changes completed?
PACFORM data, templates and form mappings ready?
Was the new or changed form printed and verified?
Metadata Changes required N/A, 45-50 Required if Error messages are changed or new programs, screens, files, index keys or functions are added to PACSES	Yes	No	N/A	Yes	No	N/A
If new messages were created was ETAB updated?
Have security buckets been created/updated?
DEST (Screen commands/primary table/functions) changes?
MSM element (entry point definitions) has been created?
Step cards (build configuration steps) have been requested?
Modifications to common routines (CR Subsystem)?

Comments – Section C

[ ]	[ ]

Developer	Date

[ ]	[ ]

Team Lead/Reviewer	Date