Automation Code Review Checklist

 A code review is a quality assurance activity to ensure that check-ins are reviewed by someone other than the author. If not pair-programming when writing the code, mature development shops often practice this activity as it’s an excellent way to catch errors early in the process. 

Automation Code Review Check List
#No	Item	Comments
1	Duplication	To avoid code redundancy and to save the development time
2	Exceptions Handling	All exceptions handled properly, even unexpected ones.
3	Framework Hacks	Test automation projects need a strong overall design strategy to make use of framework desired feature.
4	Bad Config Changes	configuration changes can have huge impacts
5	Poor Code	Organized structure is necessary for project scalability and teamwork
6	Documentation	Documentation is vital for good testing and good maintenance. When a test fails, the doc it provides significantly assist triage
7	Test Coverage	Keep the original test procedure handy, and watch out for missing coverage.
8	Hard-Coded Values	Hard-coded values often indicate hasty development
9	Typos and Bad Formatting	Typos and bad formatting reflect carelessness, cause frustration, and damage reputation.
10	Proof of Success	Tests need to run successfully in order to pass review, and proof of success (such as a log or a screen shot) must be attached to the review.