Test Proofing Protocol - RPR6320 Assurant Xmit-a

Test Proofing Protocol

Batch Process: RPR6320 Assurant Daily SVP Sales/Refunds

DEVELOPED BY APPROVED BY

NAME Jon Fortman Tim Reagan

ROLE SME/Developer Asst. Dir.

Test Proofing Protocol – RPR6320 Assurant XmitJon Fortman audit for

RSPP New Program Launch [Recur Bill Email Sourcing]

Abstract

For making any change to this program, it is imperative that full, non-compromised testing be performed. In addition to project-specific testing scenarios, the following tests scenarios must always be performed when a change has occurred to this source code unless the change is of a dire emergency. To this latter point, this is not a likely scenario. The timing of this transmission is not nearly as critical as that of the accuracy needed; it is imperative that this data going to Assurant be maintained with precision. Being late but correct is a LOT less expensive, in this case, in contrast to being “on time” but with damaged data. Fixing transmissions and doing resends can be very costly. The output file we send to Assurant is the only static data record of any kind that represents this transmission. The DB2 sourcing database is not an official record of this transmission because it is a living database. Side note: the official database of record resides with Assurant.

of 9



During development and unit testing, you will want to use small data for testing specific project-related test cases. You will need to control this by first updating SVP_ITM_XMIT_DT in SVP_ITEM to something other than NULL. Then go back and update the field with NULL for only those tkts you want to test with.

√A source code superc comparison listing must be performed between the current production version of the source code and the new version of the source code. The resulting dataset: YOURACID.SUPERC.LIST should be downloaded to a proper network directory [probably the project folder] as a text file. This should be utilized as part of the code review.

RPR6320.JFORTM1.SUPERC.LIST placed in project folder

Once you have completed project-related test scenarios, you then must do larger “A/B” type testing.An “A/B” comparison between the output of the current prod version of the program and the output of the new version of the program must be performed. For this broader testing, you will utilize all of the tkts in the Z db2 table environment. Typically in the Z db2 table environment there is a good representation of different types of transactions.

√Compile and bind the prod version of the program. Run this against all Z db2 data and capture the output file in an appropriate name.

CSVDQ.RS.RPR6320.CURRPROD.SEP13

√Compile and bind the new version of the program. Run this against all Z db2 data and capture the output file in an appropriate name different from that of the prod version file name.

CSVDQ.RS.RPR6320.ESC

Open two sessions in TSO. On one session browse the prod file and on the other session browse the test file.

PASS-The physical rec counts should be identical unless your changes are intended to eliminate or add records to the output. If your changes are not intended to reduce or add records to the output then you must find out why the rec counts are different.

According to the requirements of the project, no addition to or reduction of the rec count was expected.TEST:

-IPT- BROWSE CSVDQ.RS.RPR6320.ESC Line 00043493 Command ===> ScrolTRL00000434930060067720O0003346342A0018344666{0001182893E0000120802G******************************** Bottom of Data ********************

PROD:

-IPT- BROWSE CSVDQ.RS.RPR6320.CURRPROD.SEP13 Line 00043493 Command ===> ScrolTRL00000434930060067720O0003346342A0018344666{0001182893E0000120837I

of 9



Failed - The totals in the fields in the TRL rec should be identical unless your changes are intended to result in the totals being reduced or increased. If your changes are not intended to increase or reduce these totals, then you must find out why there is a difference.

Service plan sales tax total amounts do not match.

Test:

-IPT- BROWSE CSVDQ.RS.RPR6320.ESC Line 00043493

Command ===> ScrolRL00000434930060067720O0003346342A0018344666{0001182893E0000120802GDDFFFFFFFFFFFFFFFFFFFFDFFFFFFFFFFCFFFFFFFFFFCFFFFFFFFFFCFFFFFFFFFFC9300000434930060067720600033463421001834466600001182893500001208027

Prod:

-IPT- BROWSE CSVDQ.RS.RPR6320.CURRPROD.SEP13 Line 00043493

Command ===> Scrol

TRL00000434930060067720O0003346342A0018344666{0001182893E0000120837IEDDFFFFFFFFFFFFFFFFFFFFDFFFFFFFFFFCFFFFFFFFFFCFFFFFFFFFFCFFFFFFFFFFC39300000434930060067720600033463421001834466600001182893500001208379

FAILED - An output superc compare listing should be run between the output file produced by the current version of the program and the output file produced by your new version of the program.

The superc should only find the HDR recs being different due to the system date and timestamps. If other recs are found different then you must find out why and justify the difference. The resulting dataset: YOURACID.SUPERC.LIST should be downloaded to a proper network directory [probably the project folder] as a text file. This should be utilized as part of the code review.

531 TOTAL CHANGES

New program is outputting hex zeroes for some email fields where the email is not available. It needs to always output spaces for missing email addresses to be consistent with the way all other alphanumeric fields are being output on the file.

New:

of 9



Curr:

Differences found in the name/addr I believe are because Deborah noticed that the cust_addnl cursor was only fetching the first row in the curr prod version of the program. She changed that to pick only the ‘MDSE’ row. We need to be sure this is the cause of the differences. However, do we know for sure in prod that the MDSE row is the one that will always have the best info?

of 9



FAILED-The sysout logs from the prod and new versions are to be captured and stored in the project folder and should be identical between the two runs unless your changes are intended to alter the totaling. If your changes are not intended to alter the totaling, then you need to investigate the differences and make appropriate changes to the program.

PROD:

*********************************************** * R P R 6 3 2 0 * *********************************************** ================== PARM INPUT VALUES: ================== DATEBACK=CURDATERUN WS-TARGET-DATE SET AS: 09/13/2013 EXTRACTING SALES/REFUNDS WITH SLTKT_DT < 09/13/2013 *************************************** * R P R 6 3 2 0 * *************************************** 42790 TOTAL CURSOR FETCHES 121 CONTRACTS MARKED FOR HOLDUP AND REVIEW (QUERIED AND FETCHED BUT NO REC *************** DTL REC TYPE ********************* 42103 TOTAL NON-VALUE-DEAL NON-RECUR-BILL-EXTENSION DTL RECS WRITTEN 566 TOTAL VALUE-DEAL-RVH DTL RECS WRITTEN 5 TOTAL RECUR BILL CONTRACT EXTENSIONS WRITTEN ------- 42674 SUBTOTAL DTL RECS (SHOULD MATCH RPR6321 PROCESSING) 817 TOTAL VALUE-DEAL-RVD DTL RECS WRITTEN

of 9



*************** MISCELLANEOUS INFO *************** 745 TOTAL STAND-ALONE RSSPS FOUND 42045 TOTAL NON-STAND-ALONE RSSPS FOUND 19282 TOTAL CUST_ADDNL RETRIEVALS DONE 443 TOTAL RECURRING BILLING SALES FOUND 139 TOTAL RECURRING BILLING REFUNDS FOUND 17 WIRELESS PREMIUM PROTECTION PLANS (SALES AND REFUNDS) 191 IPHONE TRADE GUARANTEE PLANS (SALES AND REFUNDS) ************ HDR+DTL+TRL REC TYPES TOTAL ********** 1 HDR REC TYPE WRITTEN 1 TRL REC TYPE WRITTEN 43493 TOTAL RECS WRITTEN

NEW:

*********************************************** * R P R 6 3 2 0 * *********************************************** ================== PARM INPUT VALUES: ================== DATEBACK=CURDATERUN WS-TARGET-DATE SET AS: 09/13/2013 EXTRACTING SALES/REFUNDS WITH SLTKT_DT < 09/13/2013 *************************************** * R P R 6 3 2 0 * *************************************** 42790 TOTAL CURSOR FETCHES 121 CONTRACTS MARKED FOR HOLDUP AND REVIEW (QUERIED AND FETCHED BUT NO REC *************** DTL REC TYPE ********************* 42103 TOTAL NON-VALUE-DEAL NON-RECUR-BILL-EXTENSION DTL RECS WRITTEN 566 TOTAL VALUE-DEAL-RVH DTL RECS WRITTEN 5 TOTAL RECUR BILL CONTRACT EXTENSIONS WRITTEN ------- 42674 SUBTOTAL DTL RECS (SHOULD MATCH RPR6321 PROCESSING) 817 TOTAL VALUE-DEAL-RVD DTL RECS WRITTEN *************** MISCELLANEOUS INFO *************** 745 TOTAL STAND-ALONE RSSPS FOUND 42045 TOTAL NON-STAND-ALONE RSSPS FOUND 19275 TOTAL CUST_ADDNL RETRIEVALS DONE 443 TOTAL RECURRING BILLING SALES FOUND 139 TOTAL RECURRING BILLING REFUNDS FOUND 17 WIRELESS PREMIUM PROTECTION PLANS (SALES AND REFUNDS) 191 IPHONE TRADE GUARANTEE PLANS (SALES AND REFUNDS) ************ HDR+DTL+TRL REC TYPES TOTAL **********

of 9



1 HDR REC TYPE WRITTEN 1 TRL REC TYPE WRITTEN 43493 TOTAL RECS WRITTEN

PASS-Marked for holdup/review: this program will mark contracts for holdup/review by populating SVP_ITM_XMIT_DT in SVP_ITEM with special dates. i.e. 12/31/5555 or 12/31/6666. You will need to verify that the current prod version of the program and your new version are in sync in terms of what each version marks for review or does not mark for review. If there are differences in this activity, then you must find out why and justify the differences.

New and old versions: 121 CONTRACTS MARKED FOR HOLDUP AND REVIEW

PASS-<F11>Notes: this program will insert rows into db2 table CSP.CMNT_LINE for certain activities performed within the program’s processing such as marking contracts for holdup/review. These rows can be viewed in the service plan CICS screens when viewing service plan tkts by accessing the <F11>Notes panel. You will need to verify that the current prod version of the program and your new version are in sync in terms of what each version inserts into this table. If this activity is not identical, you must find out why and justify the difference.

Prod:

SELECT SVP_CNTL_ID ,-- =' ' SVP_DROP_ID ,-- =' ' ROW_LAST_MAINT_TMS ,-- =' ROW_LST_MAINT_INTL ,-- =' ' SVP_CMNT_DESC -- =' FROM CSZ.CMNT_LINE WHERE ROW_LAST_MAINT_TMS BETWEEN '2013-09-13-00.00.00.000000' AND '2013-12-31-23.59.59.000000'ORDER BY ROW_LAST_MAINT_TMS

NUMBER OF ROWS SELECTED 330

Test:

SELECT SVP_CNTL_ID ,-- =' ' SVP_DROP_ID ,-- =' ' ROW_LAST_MAINT_TMS ,-- =' ROW_LST_MAINT_INTL ,-- =' ' SVP_CMNT_DESC -- =' FROM CSZ.CMNT_LINE

of 9



WHERE ROW_LAST_MAINT_TMS BETWEEN '2013-09-13-00.00.00.000000' AND '2013-12-31-23.59.59.000000'

ORDER BY ROW_LAST_MAINT_TMS

NUMBER OF ROWS SELECTED 330

of 9

Test Proofing Protocol - RPR6320 Assurant Xmit-a

Documents

Transcript of Test Proofing Protocol - RPR6320 Assurant Xmit-a