Static Testing

What’s Static testing?Testing of Software / document / code without execution to Find defects

Why Static testing?Early testingPrevents Fault Migration & Fault multiplication

Static Testing

Typical defects that are easy to identify during Static Testing are:

Deviation from standardsMissing requirementsDesign DefectsNon maintainable code andInconsistent interface specifications

Static Testing

Benefits of Static Testing

Identifies causes (of potential failure) rather than failures

Early feedback on quality issues can be established

Detecting defects at an early stage, rework cost & time are significantly reduced

Static Testing

Benefits of Static Testing

Development productivity will be increased

Testing efficiency is improved

Static Testing

Testing

Static Testing Dynamic Testing

Review Static Analysis

Static Testing

Static Testing

Review Static Analysis

Informal Review

Walkthrough

Tech Review

Inspection

Control Flow Analysis

Data Flow Analysis

Compliance to Standards

Code Structure Metrics

Static Testing

Re-View or Second look

Systematic examination of Software / Code / Documents / Interfaces

to- Find defects- Gain understanding- Discuss & decide on best choice of solution

Static Testing

Informal Review

A Review without following any defined (formal) procedures No documentationNo prior preparation for the reviewersQuick & inexpensive way of deriving benefit

Eg: Pair Programming

Static Testing

WalkthroughAuthor led presentationAuthor systematically guiding reviewers through his workReviewers & participants Gain understandingReviewers need to be familiar with the topicSome level of documentation is maintained

Eg: Knowledge Transfer sessions (KT), Dry Runs, Scenarios

Static Testing

Technical ReviewDiscussion on Technical issues / problemsDiscussion on possible solutions and decision by consensusReview leader (Moderator) is presentAuthor can not be the Review leaderNo Management participationDocumentation is maintained

Static Testing

Formal Review / Inspection

Formal review follows a formal & defined process of review

It involves six phases

Static Testing

Formal Review / Inspection phases

1. Planning2. Kick-off3. Individual Preparation4. Review Meeting5. Rework6. Follow-up

Static Testing

PlanningSelection of personnel

-Moderator-Reviewers / Inspectors

Selection of Roles for ReviewersDefining Entry / Exit criteriaDefining Review objective

Static Testing

PlanningModerator Checks for Entry criteriaEx: i) after 30 minutes of checking no more than 3 major

defects are found on a single pageii) The document to be reviewed is available with line numbers.

iii) References needed for inspection are stable and available.

iv) Author of the document is ready to involve with review team.

Static Testing

Kick OffA formal meeting of all concerned with InspectionDocuments distributedRoles explainedReview objectives are explained

Static Testing

Kick OffReview objectivesEx: i) does the design fulfills the requirements

ii) compliance to coding standards, naming conventions etciii) maintainability and testability

Static Testing

Individual PreparationEach of the reviewers must spend time in analyzing the document under reviewPoints of conflict, issues, questions & comments to be notedA list is compiled

Static Testing

Review MeetingBusiness like meetingDiscussion is held on the list of issues identified by each of the reviewerAuthor participates and provides clarificationIf necessary Author agrees to make modificationsModerator ensures discussion is focusedScribe / Recorder records the details of discussion

Static Testing

ReworkModification / corrections are implemented for the agreed issues by the Author

Author should follow change control to trace the documents for follow-up

Static Testing

Follow-upModerator verifies whether the corrections have been achieved and correctly achieved

Moderator checks for fulfillment of the exit criteria

Moderator collects metrics related to Inspection

Static Testing

Participants in a Formal review are:ModeratorAuthorScribeReviewers andManager

Static Testing

Moderator:Moderator leads the review process

Moderator ensures discussion is focused

Moderator ensures that all reviewers participate effectively in review meeting

Moderator verifies whether or not the reviewers are adequately prepared on the documents before the review meeting

Moderator performs the entry check and the follow-up on the rework

Static Testing

Author:As the writer of the document he/she should learn as much as possible to improve the quality of the documents

Clarify unclear areas to the reviewers

Understand the defects found

Implement agreed corrections

Static Testing

Scribe :The scribe has to record details of discussion during review meeting and also note defects identified

Develops ‘List of Corrections’, Minutes of Meeting etc

Reviewers :Checks for defects in the documents under review

Static Testing

Manager:

Doesn’t participate in a review process unless Management documents are being reviewed

Allocate time & resources in project schedules

Involves in selection of Moderator

Static Testing

Factors contributing to the success of Reviews

Review must have clear objective

Defects found must be welcomed

Proper personnel must be involved with reviews

Proper level of review must be selected

Use of Check list & Role-play must be encouraged

Adequate resources & time must be provided