8/12/2019 Unit Test Cases Template

1/3

UNIT TEST CASES TEMPLATE:

Step

#

Description Test Conditions Expected Results

ActualResults, Pass orFail

(P or F)

TestedBy

SAP-

CMS

Inter

faces

1 Check for thetotal count ofrecords insource tablesthat is fetched

and the totalrecords in thePRCHG tablefor a perticularsessiontimestamp

SOURCE:

SELECT count(*) FROMXST_PRCHG_STG

TARGET:

Select count(*) from_PRCHG

Both the source and targettable load record countshould match.

Should besame as theexpected

Pass Stev

2 Check for allthe targetcolumnswhether theyare gettingpopulatedcorrectly withsource 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 targettable record values shouldreturn zero records

Should besame as theexpected

Pass Stev

3 Check forInsert strategyto load records

into targettable.

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 dataShould besame as theexpected

Pass Stev

8/12/2019 Unit Test Cases Template

2/3

Step

#

Description Test Conditions Expected Results

Actual

Results,

Pass or

Fail

(P or F)

Tested

By

4 Check forUpdate

strategy to loadrecords intotarget table.

Identify a one Record from

the source which is already

present in the target tablewith different

PRCHG_ST_CDE or

PRCHG_TYP_CDE values

Then run the session

It should update record intotarget table with source

data for that existing record

Should besame as the

expected

Pass Stev

QA Process Cycle:

Software QA involves the entire software development PROCESS - monitoring and improving

the process.

The philosophy of Quality Assurance for software systems development is to ensure the system

meets or exceeds the agreed upon requirements of the end-users; thus creating a high-quality,fully-functional and user-friendly application.

Phase I: Requirements Gathering, Documentation and Agreement

Phase II: Establishing Project Standards

Phase III: Test Planning

Phase IV: Test Case Development

Phase V: QA Testing

Phase VI: User Acceptance Testing

Phase VII: System Validation

QA Life Cycle consists of 5 types of

Testing regimens:

1. Unit Testing

2. Functional Testing

3. System Integration Testing4. 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

8/12/2019 Unit Test Cases Template

3/3

Functional Testing:The testing of all the applications modules individually to ensure themodules, 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 sameenvironment, database instance, network and inter-related applications, as it would function inproduction. This includes security, volume and stress testing.

User Acceptance Testing(UAT):The testing of the entire application by the end-usersensuring the application functions as set forth in the system requirements documents and that thesystem meets the business needs