This tutorial covers area 7 of the Certified Software Test Professional requirements. This tutorial also counts as an elective towards the requirements of the Certified Test Manager (CTM) certification.

When the test team receives a requirement document in order to design their tests, most often, that document is vague and high level. Of course, test engineers try to ask as many questions as they can but very often they do not even know what to ask. When developers get the same vague high level requirement document, they too try to ask questions but sometimes just make assumptions about the missing details. In all cases, The test team remains uninformed of any changes in the requirements. The end result is a test design that never covers everything in code. In order to overcome this problem, test professionals need to learn how to capture details and ask questions during requirement reviews, design reviews and code reviews. This is where static testing comes to play.

This course will examine the different elements that make an effective static testing process

• Why we want to plan
• How to create a plan for your testing project
• What to include in the test plan document
• How to effectively apply the plan

• Introduction
  • Why inspection and reviews are important
  • Why do most inspection and reviews programs fail
  • What to inspect and when
  • Four different variations of inspections and reviews
  • Validation vs Verification
  • Peer review in CMM Level 3
• Elements of the Static Testing Process
  • Roles in the static process
  • The seven different elements
    • Planning
    • Overview meeting
    • Preparation
    • Inspection meeting
    • Record keeping and reporting
    • Rework and follow-up
    • Causal analysis
• A Peer review Workshop
• Establishing a Static inspection process
  • Why a process
  • Characteristics of an effective process
  • Steps to establishing the inspection process:
    • Gather relevant information
    • Define a standard inspection process
    • Define a number of variations of the process for different situations
    • Train personnel on different aspects of the process
    • Try each process variation for its intended use
    • Monitor and continuously improve each process variation