Download as pdf or txt
Download as pdf or txt
You are on page 1of 1

Automated Test Review Checklist

Project Code
Version of the work product
Reviewer(s)
Review date
Work product' size
Effort spent on review (man-hour)

Question Yes No N/A Note

DOCUMENT CONTROL
Is there any design documents for automated test? If yes
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?
AUTOMATED TEST IMPLEMENTATION
Is there any standard methodologies of testing automation used? (If
yes, pls name it in the Comment section below)
Is any scripting convention used? If yes
Is it reviewed and approved?
Is there any test script review records?
Is test script test report/defect log available?
Is there evidence of that the test scripts are approved before using
for test the software product?
Does CM activities for automated test follow the CM plan?
Are the automated test reports created and processed following the
procedure defined in the test plan?
<Add more rows if needed>

* Comments
Functional automated test:
Automated test case coverage (Number of automated TCs/Total
TCs (%))

* Suggestion

[ ] - Pass
[ ] - Review again
[ ] - Other

08ce-CL/PM/HDCV/FSOFT 1/0

You might also like