Unit 1.4: Static and Dynamic Testing

1. Definitions

Static Testing:

• Testing involves verifying the software without executing the code.
• It involves reviewing documents, code, and design.
• Goal: To find defects early in the life cycle (typos, bad logic, missing requirements).

Dynamic Testing:

• Testing involves executing the code and validating the output.
• This is what we traditionally call "testing" (clicking buttons, running scripts).
• Goal: To validate functional behavior and performance.

2. Types of Static Testing

A. Inspection (Formal):

• Most formal type of review.
• Led by a trained "Moderator".
• Involves a team (Author, Reader, Recorder, Inspector).
• Follows a strict checklist and entry/exit criteria.

B. Walkthrough (Informal):

• Led by the Author of the code/document.
• The author guides the team through the document to gather feedback.
• No strict process; aimed at learning and understanding.

C. Technical Review:

• A peer review focused on technical correctness.
• Less formal than inspection but more structured than a walkthrough.
• Ensures adherence to coding standards.

3. Comparison Table

4. Limitations of Testing

• Cannot prove absence of defects: (Principle 1).
• Time Constraints: We always have a deadline; we can't test forever.
• Resource Constraints: Limited budget and hardware.
• Logical Limitations: We cannot test every possible input (e.g., a calculator adding all numbers).
• Oracle Problem: Sometimes it is difficult to know what the "correct" output should be.