Scribd
Upload
5 views3 pages

Static Testing Review Notes

Static testing evaluates software artifacts without executing code, aiming to detect defects early and improve software quality. The review process consists of planning, preparation, a review meeting, rework, and follow-up, with techniques including informal walkthroughs and formal inspections. Advantages of static testing include reduced costs, improved productivity, and better team communication.

Uploaded by

shreyasbhatk.scs24
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
5 views3 pages

Static Testing Review Notes

Static testing evaluates software artifacts without executing code, aiming to detect defects early and improve software quality. The review process consists of planning, preparation, a review meeting, rework, and follow-up, with techniques including informal walkthroughs and formal inspections. Advantages of static testing include reduced costs, improved productivity, and better team communication.

Uploaded by

shreyasbhatk.scs24
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Static Testing and Review Techniques – Study

Notes

1. What is Static Testing?

Static testing is the process of evaluating software artifacts without executing the program.

• Requirement documents

• Design documents

• Source code

• Test plans

Purpose of Static Testing

• Detect defects early in development

• Improve software quality

• Reduce cost and time of fixing errors later

2. Review Process Steps

Step 1: Planning

• Identify the document to be reviewed

• Define entry and exit criteria

• Assign participants

• Explain review objectives

Step 2: Preparation (Individual Work)

• Participants review the document individually

• Identify defects

• Mark questions or comments

• Record findings

Step 3: Review Meeting

• Discuss defects found


• Suggest improvements

• Record issues

Step 4: Rework

• Author fixes defects found during the review

• Document is updated

Step 5: Follow-Up

• Moderator verifies defects are fixed

• Exit criteria are checked

3. Review Techniques

Walkthrough

Walkthrough is an informal review meeting led by the author of the document.

• Author explains the document step by step

• Team members review the content

• Participants suggest improvements or defects

Inspection

Inspection is a formal review process conducted by a trained moderator.

• Very structured process

• Uses checklists and rules

• Focus on identifying defects

Inspection Process

• Pre-meeting preparation by participants

• Inspection meeting to discuss defects

• Inspection report prepared

• Post-inspection follow-up to ensure corrections

Entry and Exit Criteria


Entry Criteria

• Document is complete

• Participants are available

• Checklist prepared

Exit Criteria

• Defects documented

• Corrections implemented

• Review objectives achieved

Advantages of Static Testing

• Early defect detection

• Reduced cost and development time

• Improved productivity

• Detection of missing or incorrect requirements

• Better team communication

Summary

Static testing evaluates software artifacts without executing code. The review process includes
planning, preparation, review meeting, rework and follow-up. Walkthroughs are informal reviews led
by the author, while inspections are formal reviews led by a moderator. Static testing helps detect
defects early, reduces development cost and improves overall software quality.

You might also like