Scribd
Upload
497 views12 pages

Test Case Review Checklist-Project - Version

This document provides a checklist for reviewing system test cases. It contains prerequisites for test cases, such as baselining input documents and separating positive and negative test scenarios. The checklist then lists validation steps for ETL, Teradata, and non-functional test cases to ensure things like requirements coverage, table and data validation, and job scheduling are tested. Test cases are also checked to see if they are available in the defect tracking system.

Uploaded by

manjunathganguly771275
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
497 views12 pages

Test Case Review Checklist-Project - Version

This document provides a checklist for reviewing system test cases. It contains prerequisites for test cases, such as baselining input documents and separating positive and negative test scenarios. The checklist then lists validation steps for ETL, Teradata, and non-functional test cases to ensure things like requirements coverage, table and data validation, and job scheduling are tested. Test cases are also checked to see if they are available in the defect tracking system.

Uploaded by

manjunathganguly771275
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
You are on page 1/ 12

This document is intend to provide a checklist for the users to review

User need to follow this checklist during system test case review proc
tracker.
Once rework is done based on review comments, test cases need to
in-line with business requirements in scope.

st for the users to review the system test cases.

tem test case review process and log all review defects in the defect

ments, test cases need to be reviewed again to ensure test case is

Sl#

Version#

Date

Template Revision History


Author

Revision History
Comment

Pre-Requisites:
============
1. All input documents should be baselined
2. Test functionality/goal should drill down into test scenarios to make test case m
3. Test steps should be clear to instruct the user how to proceed
4. Positive and negative test scenarios should be separated

narios to make test case more manageable


proceed
ated

Project Name
Module
Reviewer
Review Date
Test Case Developer Name
Time Spent for review (in Mins)

Sl#
Description
Verify ETL Test Cases
All functionaly are covered as per the test goal
1
2

All related Unix/Linux server paths to run graphs/psets


are clearly mentioned in the test case

All graph/psets names are mentioned clearly in the


test case.
Inbound and outbound processes are mentioned
4
separately
Output file/data validation is mentioned in the test
5
case.
Test case includes error handling- negative test
6
scenarios for the test goal
Verify Teradata Test Cases
Table name is clearly mentioned in the test case
7
3

Table structure mentioned in the test case is matching


with what is mentioned in detailed design document

Data validation for tables is mentioned in the test case

Verify whether key constraints for targets are


mentioned in the test cases
Verify whether ETL execution details - e.g. which
11
graph needs to be run with what input file etc. are
mentioned in the test case
Verify fact and dimension table verification is
12
mentioned in the test case
Verify impacted tables are mentioned in downstream
13
data marts
Verify non impacted tables are mentioned in
14
downstream data marts- as per the scope
Verify surrogate keys verification is mentioned in the
15
test case- as per the scope
Verify whether test data available to create SQL with
16
different logic for data consistent validation
Verify attribute level test steps/scenarios are available
17
matching with mapping sheet
Verify Non-Functional requirements
Verify whether all non-functional requirements are
18
covered as per the scope
Verify TWS jobs requirements
10

Status

Comment

19
20

Verify job scheduling is covered in the test case


Verify all job names are covered in test case

Comment

Sl#
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22

Test Case Name

All review
checkpoints covered

Test Case Status

Available in HPQC

Comment

You might also like