Wednesday, March 3, 2010

REVIEW CHECKLIST for Automation Script

REVIEW CHECKLIST
Script Name:

Planning/Action Step Review Compliance
Maintainability "Do You understand the Script You are reviewing
(Are the names used meaningful and logical)"
Does the Script implements the desired functionality as per the Scenario of Test Case document?
Are the Error/Confirmation messages or input values hard coded?
Are there proper comments for wait () statements, mentioning the reason why sleep has been included?
Are there proper comments include for the modifications done?
Is it using the credit card information from central repository?
If it is a booking script, is it logging the ORL to the central excel sheet?
is the email id used is from central data table?
Is it a GR path? If yes, how is email id generation handled?
Delete cookie is included at the top of the script?
Is proper credit card used as per the module?

Reusability Are the functions that are used defined in the Utility files ?
Is there any repeated code present in the script file?
Is the implementation optimized?
Is this a repeated script/code/functionality?

Coding Standard Are the naming conventions followed for scripts, functions and variables?
Are there necessary Comments that reflect the Scenario or Test Case document?
Are there variables that are declared but never used in the Script?
Is the email id used is proper?
Has the documentation done in the script.
If there are static functions defined, are the properly commented(Remember that a static function should always start with _orb)
"Do the following lines appear at the top of script?
report_msg(""Running against platform: "" & platform);
report_msg(""Using user: "" & test_props[""email""]);"
"Do the following lines appear at the bottom of script?
report_msg(""END OF TEST"");
"
Are the data table statements used properly?
Do all the values such as Script ownership, status..etc are set for the script in QC?


Indentation Are the used variables declared at the top of the Script File and are they properly commented?
Has sufficient care taken on indentation of the script statements, logical loops, messages, etc,?

Execution Has the Test Case executed devoid of any errors and exceptions
Does the script pass through QC?

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.