ISTQB Static Testing foundation level in QA

ISTQB

1. Static Testing
What’s Static testing?
Testing of Software / document / code without
execution to Find defects
Why Static testing?
Early testing
Prevents Fault Migration & Fault multiplication

2. Static Testing
Typical defects that are easy to identify
during Static Testing are:
Deviation from standards
Missing requirements
Design Defects
Non maintainable code and
Inconsistent interface specifications

3. 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

4. Static Testing
Benefits of Static Testing
Development productivity will be increased
Testing efficiency is improved

5. Static Testing
Testing
Static TestingDynamic Testing
Review Static Analysis

6. 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

7. 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

8. Static Testing
Informal Review
A Review without following any defined (formal)
procedures
No documentation
No prior preparation for the reviewers
Quick & inexpensive way of deriving benefit
Eg: Pair Programming

9. Static Testing
Walkthrough
Author led presentation
Author systematically guiding reviewers through
his work
Reviewers & participants Gain understanding
Reviewers need to be familiar with the topic
Some level of documentation is maintained
Eg: Knowledge Transfer sessions (KT), Dry
Runs, Scenarios

10. Static Testing
Technical Review
Discussion on Technical issues / problems
Discussion on possible solutions and decision by
consensus
Review leader (Moderator) is present
Author can not be the Review leader
No Management participation
Documentation is maintained

11. Static Testing
Formal Review / Inspection
Formal review follows a formal & defined
process of review
It involves six phases

12. Static Testing
Formal Review / Inspection phases
1.Planning
2.Kick-off
3.Individual Preparation
4.Review Meeting
5.Rework
6.Follow-up

13. Static Testing
Planning
Selection of personnel
-Moderator
-Reviewers / Inspectors
Selection of Roles for Reviewers
Defining Entry / Exit criteria
Defining Review objective

14. Static Testing
Planning
Moderator Checks for Entry criteria
Ex: i) after 30 minutes of checking no more than 3 major
defects are found on a single page
ii) 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.

15. Static Testing
Kick Off
A formal meeting of all concerned with
Inspection
Documents distributed
Roles explained
Review objectives are explained

16. Static Testing
Kick Off
Review objectives
Ex: i) does the design fulfills the requirements
ii) compliance to coding standards, naming conventions etc
iii) maintainability and testability

17. Static Testing
Individual Preparation
Each of the reviewers must spend time in
analyzing the document under review
Points of conflict, issues, questions &
comments to be noted
A list is compiled

18. Static Testing
Review Meeting
Business like meeting
Discussion is held on the list of issues
identified by each of the reviewer
Author participates and provides clarification
If necessary Author agrees to make
modifications
Moderator ensures discussion is focused
Scribe / Recorder records the details of
discussion

19. Static Testing
Rework
Modification / corrections are implemented
for the agreed issues by the Author
Author should follow change control to trace
the documents for follow-up

20. Static Testing
Follow-up
Moderator verifies whether the corrections
have been achieved and correctly achieved
Moderator checks for fulfillment of the exit
criteria
Moderator collects metrics related to
Inspection

21. Static Testing
Participants in a Formal review are:
Moderator
Author
Scribe
Reviewers and
Manager

22. 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

23. 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

24. 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

25. 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

26. 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