Unit Test Plan(UTP)
Testing regimens:
1. Unit Testing
2. Functional Testing
3. System Integration Testing
4. User Acceptance Testing
Unit testing: The testing, by development, of the application modules to verify each unit (module) itself meets the accepted user requirements and design and development standards
Functional Testing: The testing of all the applications modules individually to ensure the modules, as released from development to QA, work together as designed and meet the accepted user requirements and system standards
System Integration Testing: Testing of all of the application modules in the same environment, database instance, network and inter-related applications, as it would function in production. This includes security, volume and stress testing.
User Acceptance Testing(UAT): The testing of the entire application by the end-users ensuring the application functions as set forth in the system requirements documents and that the system meets the business needs.
UTP Template:
Step # | Description | Test Conditions | Expected Results | Actual Results, | Pass or Fail (P or F) | Tested By |
SAP- CMS Interfaces | ||||||
1 | Check for the total count of records in source tables that is fetched and the total records in the PRCHG table for a perticular session timestamp | SOURCE: SELECT count(*) FROM XST_PRCHG_STG TARGET: Select count(*) from _PRCHG | Both the source and target table load record count should match. | Should be same as the expected | Pass | Stev |
2 | Check for all the target columns whether they are getting populated correctly with source data. | select PRCHG_ID, PRCHG_DESC, DEPT_NBR, EVNT_CTG_CDE, PRCHG_TYP_CDE, PRCHG_ST_CDE, from T_PRCHG MINUS select PRCHG_ID, PRCHG_DESC, DEPT_NBR, EVNT_CTG_CDE, PRCHG_TYP_CDE, PRCHG_ST_CDE, from PRCHG | Both the source and target table record values should return zero records | Should be same as the expected | Pass | Stev |
3 | Check for Insert strategy to load records into target table. | Identify a one record from the source which is not in target table. Then run the session | It should insert a record into target table with source data | Should be same as the expected | Pass | Stev |
4 | Check for Update strategy to load records into target table. | Identify a one Record from the source which is already present in the target table with different PRCHG_ST_CDE or PRCHG_TYP_CDE values Then run the session |
