Making Code Reviews
First of all , i will tell you about reviews. what is the need and goal of reviews in software testing.
Review: A process or meeting during which a work product, or set of work products, is presented to project personnel,managers, users, customers, or other interested parties for approval.
The main goal of review is to find defects at early stages of development. Types of reviews include Management reviews, Technical Reviews, Inspections, Walkthroughs and Audits. Code Reviews is the part of Technical Reviews in the testing. Now,
What is Code Review ?
A meeting at which software code is presented to project personnel, managers,users, customer, or other interested parties for comments.
Who is involved in Code Review ?
QA Team member ( In case the QA Team is only involved in Black Box Testing, then the development team lead chairs the review team) leads code review. Members from development team and QA team participate in the review.
Input Criteria
The coding standard document and the source file are the essential documents for the review. A checklist can be used for review.
Exit Criteria
Exit criteria include the filled & completed checklist with the reviewer's comments and suggestions and the re-verification whether they are incorporated in the documents.
Ashish Darji,
QA,
Dev Information Technology Pvt. Ltd.
mail: