Chapter 3: Static Testing

Question 1

What are the 10 Static Testing Basics work product examined?

Answer 1

 Specifications, including business requirements, functional requirements, and security
requirements
 Epics, user stories, and acceptance criteria
 Architecture and design specifications
 Code
 Testware, including test plans, test cases, test procedures, and automated test scripts
 User guides
 Web pages
 Contracts, project plans, schedules, and budget planning
 Configuration set up and infrastructure set up
 Models, such as activity diagrams, which may be used for Model-Based testing (see ISTQBCTFL-MBT and Kramer 2016)

Question 2

What are the Additional benefits of static testing?

Answer 2

Detecting and correcting defects more efficiently, and prior to dynamic test execution
 Identifying defects which are not easily found by dynamic testing
 Preventing defects in design or coding by uncovering inconsistencies, ambiguities, contradictions,
omissions, inaccuracies, and redundancies in requirements
 Increasing development productivity (e.g., due to improved design, more maintainable code)
 Reducing development cost and time
 Reducing testing cost and time
 Reducing total cost of quality over the software’s lifetime, due to fewer failures later in the
lifecycle or after delivery into operation
 Improving communication between team members in the course of participating in reviews

Question 3

What are the Differences between Static and Dynamic Testing?

Answer 3

One main distinction is that static testing finds defects in work products directly rather than identifying
failures caused by defects when the software is run. A defect can reside in a work product for a very long
time without causing a failure. The path where the defect lies may be rarely exercised or hard to reach, so
it will not be easy to construct and execute a dynamic test that encounters it. Static testing may be able to
find the defect with much less effort. requirements defects, design..

Question 4

What is the Work Product Review Process?

Answer 4

Planning
Initiate review
Individual review
Issue communication and analysis 
Fixing and reporting

Question 5

What are the Work Product Review Process?

Answer 5

Planning
 Defining the scope, which includes the purpose of the review, what documents or parts of
documents to review, and the quality characteristics to be evaluated
 Estimating effort and timeframe
 Identifying review characteristics such as the review type with roles, activities, and checklists
 Selecting the people to participate in the review and allocating roles
 Defining the entry and exit criteria for more formal review types (e.g., inspections)
 Checking that entry criteria are met (for more formal review types)
Initiate review
 Distributing the work product (physically or by electronic means) and other material, such as
issue log forms, checklists, and related work products   Answering any questions that participants may have about the review
Individual review (i.e., individual preparation)  Reviewing all or part of the work product
 Noting potential defects, recommendations, and questions
Issue communication and analysis  Communicating identified potential defects (e.g., in a review meeting)  Analyzing potential defects, assigning ownership and status to them  Evaluating and documenting quality characteristics  Evaluating the review findings against the exit criteria to make a review decision (reject; major
changes needed; accept, possibly with minor changes)
Fixing and reporting
 Creating defect reports for those findings that require changes to a work product  Fixing defects found (typically done by the author) in the work product reviewed  Communicating defects to the appropriate person or team (when found in a work product related
to the work product reviewed)  Recording updated status of defects (in formal reviews), potentially including the agreement of
the comment originator  Gathering metrics (for more formal review types)  Checking that exit criteria are met (for more formal review types)  Accepting the work product when the exit criteria are reached