TESTING - II

 

Objectives

• To perform code walk through, Manual Testing and Automation

Description

The level of the code walkthough is determined by the extent of the code changes to be reviewed.   Complexity of the changes, extent of the changes, and criticality of the changes all play into the decision of place/location of the code walkthrough. The Developer makes a recommendation for the appropriate level of the code walkthrough.   The Project Lead may override that recommendation.

Various level/types of the code walkthrough are:    

• Waived: Code walkthrough is waived due to a very simple algorithm change (or configuration file), and not in a critical point in the code.

• Informal: Code is presented to the reviewer who simply reviews it "on-the-spot".  This is reserved for simple, confined, and non-critical changes.

• Formal: Code is presented to the reviewer and the reviewer examines the code and algorithms for proper style, format, and technique.  This is reserved for complex code changes of a critical nature and those changes that may impact multiple subsystems.

In addition based on the complexity, extent, and criticality of the changes, as well as the reviewer's knowledge of the design and implementation, the code walkthrough may be conducted independently by the reviewer, rather than have the developer do a presentation or be present.  If the reviewer has questions, then the reviewer is responsible for seeking out the developer to answer the questions.

Tools

No specific tool will be used in this lab.

Procedure

Code is reviewed for the following:

• Clarity and Readability - as in accordance to the coding standards.

• Requirements Met - code does what it is supposed to do.

• Performance - code is written to prevent performance problems

• Algorithms and error situations - algorithm used is sound, error conditions handled, all reasonable conditions are handled.

At least two people are required for the code walkthrough:

• Developer - who writes the code

• Reviewer - who reviews the code

Problem

Prepare a checklist of items that should be checked during code walkthrough.

Deliverables

There can be three outcomes to the code walkthrough:

• Successful: all required checks and quality are present.  Software may be released into the approved build.

• Corrective action needed. No further review Needed:  a list of items to be corrected are presented.  Once these are performed, the code walkthrough is complete.

• Corrective Action Needed, Review Needed: a list of items to be corrected are presented.  One these are performed, another code walkthrough is warrented.

References                                                                                              

 

• David Gustafson: Software Engineering, Schaum's Outline Series, McGraw Hill, 2002, pg. 145-157

• Roger S. Pressman: Software Engineering A Practitioner's Approach, 7th Edition, McGraw Hill, 2010, pg. 420-459

• Pankaj Jalote: A Concise Introduction to Software Engineering , Springer, 2008, pg. 225-252