UNIT TESTING IN INFORMATICA

Unit testing can be broadly classified into 2 categories.
Quantitative Testing
Validate your Source and Target
a) Ensure that your connectors are configured properly.
b) If you are using flat file make sure have enough read/write permission on the file share.
c) You need to document all the connector information.
Analyze the Load Time
a) Execute the session and review the session statistics.
b) Check the Read and Write counters. How long it takes to perform the load.
c) Use the session and workflow logs to capture the load statistics.
d) You need to document all the load timing information.
Analyze the success rows and rejections.
a) Have customized SQL queries to check the source/targets and here we will perform the Record Count Verification.
b) Analyze the rejections and build a process to handle those rejections. This requires a clear business requirement from the business on how to handle the data rejections. Do we need to reload or reject and inform etc? Discussions are required and appropriate process must be developed.
Performance Improvement
a) Network Performance
b) Session Performance
c) Database Performance
d) Analyze and if required define the Informatica and DB partitioning requirements.
Qualitative Testing
Analyze & validate your transformation business rules. More of functional testing.
e) You need review field by field from source to target and ensure that the required transformation logic is applied.
f) If you are making changes to existing mappings make use of the data lineage feature Available with Informatica Power Center. This will help you to find the consequences of Altering or deleting a port from existing mapping.
g) Ensure that appropriate dimension lookup’s have been used and your development is in Sync with your business requirements.

NOTE:
for more information Please refer INFORMATICA REALTIME UNIT TESTING in the same BLOG(how to integrate more than once source)

 

1. UNIT TEST CASE FOR LOAN_MASRER

FUNCTIONALITY_ID	FIELD_NAME	DETAIL	VALUE PASSED	EXPECTED RESULT	ACTUAL RESULT	PASS/FAIL RESULT	REMARK
STG_SCHM_DTLS_001	LOAN _ID	_TYPE_ID SHOULD BE NOT NULL ,FIRST CHARACHER ALPHABET(INSCH) AND LAST 10 CHARACTER NUMERIC VALUES AND ALSO ITS LENGTH IS 16	INSCH00000000002	ACCEPT RECORD	RECORD ACCEPTED	PASS
STG_SCHM_DTLS_002	LOAN_TYPE_ID	REJECT WHEN , NOT NULL ,FIRST 5 CHARACHER NOT (INSCH) OR LAST 10 CHARACTER NON NUMERIC VALUES AND ALSO ITS LENGTH <>16	INSCP001000000002	REJECT RECORDRECORD REJECTED	PASS	RECORD INSERTED INTO REJECTED FILE WITH AN ERROR_ID &ERROR_DETAILS INTO ERROR_TABLE
STG_SCHM_DTLS_003	LOAN_COMPANY_ID	LOAN_COMPANY_ID  MUST BE NOT NULL,FIRST 4 CHRACTER ALPHABET(INCO) AND LAST 11 CHRACTER NUMERIC VALUES AND ALSO LENGTH IS 15	INCO00000000003	ACCEPT RECORD	RECORD ACCEPTED	PASS
STG_SCHM_DTLS_004	LOAN_COMPANY_ID	REJECT WHEN , NOT NULL ,FIRST 4 CHARACHER NOT (INCO) OR LAST 11 CHARACTER NON NUMERIC VALUES AND ALSO ITS LENGTH <>15	INSO00000060003	REJECT RECORD	RECORD REJECTED	PASS	RECORD INSERTED INTO REJECTED FILE WITH AN ERROR_ID &ERROR_DETAILS INTO ERROR_TABLE
STG_SCHM_DTLS_005	START_DATE	START DATE SHOULD  BE  A VALID DATE	12/9/1988	ACCEPT RECORD	RECORD ACCEPTED	PASS
STG_SCHM_DTLS_006	START_DATE	START DATE SHOULD NOT BE LOADED WHEN IT IS NOT A VALID DATE	33FeB/88	REJECT RECORD	RECORD REJECTED	PASS	RECORD INSERTED INTO REJECTED FILE WITH AN ERROR_ID &ERROR_DETAILS INTO ERROR_TABLE
STG_SCHM_DTLS_007	SCHEME_DESC	SCHEME-DESC SHOULD BE ALPHABETIC TYPE	AUTOMOBILE	ACCEPT RECORD	RECORD ACCEPTED	PASS
STG_SCHM_DTLS_008	SCHEME_DESC	REJECT WHEN SCHEME DISCOUNT IS NOT ALPHABETIC TYPE	MOTO124	REJECT RECORD	RECORD REJECTED	PASS	RECORD INSERTED INTO REJECTED FILE WITH AN ERROR_ID &ERROR_DETAILS INTO ERROR_TABLE
STG_SCHM_DTLS_009	PREMIUM_PER_LACS	PREMIUM_PER_LACSSHOULD BE NUMERIC	5000	ACCEPT RECORD	RECORD ACCEPTED	PASS