13
This document is intend to provide a cases. User need to follow this checklist d review defects in the defect tracker Once rework is done based on review ensure test case is in-line with bus

Test Case Review Checklist-Project_version

Embed Size (px)

DESCRIPTION

dssd

Citation preview

GeneralThis document is intend to provide a checklist for the users to review the system test cases.

User need to follow this checklist during system test case review process and log all review defects in the defect tracker.

Once rework is done based on review comments, test cases need to be reviewed again to ensure test case is in-line with business requirements in scope.

Revision HistoryTemplate Revision HistorySl#Version#DateAuthorComment

Pre-RequisitePre-Requisites:============1. All input documents should be baselined2. Test functionality/goal should drill down into test scenarios to make test case more manageable3. Test steps should be clear to instruct the user how to proceed4. Positive and negative test scenarios should be separated

Test Case Review ChecklistProject NameModuleReviewerReview DateTest Case Developer NameTime Spent for review (in Mins)Sl#DescriptionStatusCommentVerify ETL Test Cases1All functionaly are covered as per the test goal2All related Unix/Linux server paths to run graphs/psets are clearly mentioned in the test case3All graph/psets names are mentioned clearly in the test case.4Inbound and outbound processes are mentioned separately5Output file/data validation is mentioned in the test case.6Test case includes error handling- negative test scenarios for the test goalVerify Teradata Test Cases7Table name is clearly mentioned in the test case8Table structure mentioned in the test case is matching with what is mentioned in detailed design document9Data validation for tables is mentioned in the test case10Verify whether key constraints for targets are mentioned in the test cases11Verify whether ETL execution details - e.g. which graph needs to be run with what input file etc. are mentioned in the test case12Verify fact and dimension table verification is mentioned in the test case13Verify impacted tables are mentioned in downstream data marts14Verify non impacted tables are mentioned in downstream data marts- as per the scope15Verify surrogate keys verification is mentioned in the test case- as per the scope16Verify whether test data available to create SQL with different logic for data consistent validation17Verify attribute level test steps/scenarios are available matching with mapping sheetVerify Non-Functional requirements18Verify whether all non-functional requirements are covered as per the scopeVerify TWS jobs requirements19Verify job scheduling is covered in the test case20Verify all job names are covered in test case

Summary SheetSl#Test Case NameAll review checkpoints coveredTest Case StatusAvailable in HPQCComment12345678910111213141516171819202122