This document is a test case review checklist used to evaluate test cases for a project. It contains questions to verify document control procedures were followed and whether test cases cover requirements, testing types, include unique identifiers, specify actions, test conditions, expected results, and more. Reviewers are asked to indicate whether each item passes, needs re-review, or has other feedback, and can provide notes on any item.
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
0 ratings0% found this document useful (0 votes)
289 views3 pages
Checklist - Test Case Review
This document is a test case review checklist used to evaluate test cases for a project. It contains questions to verify document control procedures were followed and whether test cases cover requirements, testing types, include unique identifiers, specify actions, test conditions, expected results, and more. Reviewers are asked to indicate whether each item passes, needs re-review, or has other feedback, and can provide notes on any item.
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/ 3
Test Case Review Checklist
Project Code: Version of the work product: Reviewer(s): Review date:<DD-MMM-DD> Number of test cases: Effort spent on review (person-hour):
Question Yes No N/A
DOCUMENT CONTROL Verify whether document control procedures have been followed by checking for the following: Does the title page contain the document name, version number, release date and issued date? Does the header and footer correctly specify the name, and version of the document? Does the page – numbering scheme indicate the total number of pages in the document? Is the history traceable? Does it include list of reference documents? Are all documents checked Spelling and Grammar in MS Word or similar tools? TEST CASE REVIEW CHECKLIST Do test cases cover all requirements? Do test cases cover all Testing types described in Test plan? Has each test case been assigned a test case identifier? Does each test case specify: Actions Test condition Expected result Have the expected results been recorded in detail? Do test cases for field validations, record validations and database updates include the following? Valid conditions Invalid conditions Boundary or unusual conditions Is error message/message code specified in expected result for abnormal cases? Do the test cases for reports include the test data along with the expected output? Have the inter test case dependencies been described? Have all requested environments been specified ? Are pre-conditions for the test specified? Are all metrics of test cases meet standards?
Software Asset Management: What Is It and Why Do I Need It?: A Textbook on the Fundamentals in Software License Compliance, Audit Risks, Optimizing Software License ROI, Business Practices and Life Cycle Management