Scribd
Upload
29 views26 pages

Static Testing

Static testing involves analyzing software, code, or documents without executing them in order to find defects. It helps identify defects early in the development process before they can multiply or migrate. Common defects found through static testing include deviations from standards, missing requirements, design defects, and inconsistent specifications. Static testing provides benefits like reducing rework costs and time, improving efficiency, and increasing productivity. Common static testing techniques include reviews, analysis, inspections, walkthroughs, and technical reviews. Formal reviews follow a defined multi-phase process involving planning, overview, preparation, meeting, rework, and follow up.

Uploaded by

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

Static Testing

Static testing involves analyzing software, code, or documents without executing them in order to find defects. It helps identify defects early in the development process before they can multiply or migrate. Common defects found through static testing include deviations from standards, missing requirements, design defects, and inconsistent specifications. Static testing provides benefits like reducing rework costs and time, improving efficiency, and increasing productivity. Common static testing techniques include reviews, analysis, inspections, walkthroughs, and technical reviews. Formal reviews follow a defined multi-phase process involving planning, overview, preparation, meeting, rework, and follow up.

Uploaded by

duby86
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 26

Static Testing

Whats Static testing?

Testing of Software / document / code


without execution to Find defects
Why Static testing?

Early testing

Prevents Fault Migration & Fault


multiplication
Static Testing
Typical defects that are easy to
identify during Static Testing
are:

Deviation from standards

Missing reuirements

Design Defects

!on maintaina"le code and

#nconsistent interface speci$cations


Static Testing
Benefts of Static Testing

#denti$es causes %of potential failure&


rather than failures

Early feed"ac' on uality issues can


"e esta"lished

Detecting defects at an early stage(


rewor' cost & time are signi$cantly
reduced
Static Testing
Benefts of Static Testing

Development productivity will "e


increased

Testing e)ciency is improved


Static Testing
Testing
Static
Testing
Dynamic
Testing
Revie
Static
!nalysis
Static Testing
Static
Testing
Revie
Static
!nalysis
"nformal
Revie
Wal#throu
gh
Tech
Revie
"nspection
$ontrol Flo
!nalysis
Data Flo
!nalysis
$ompliance to
Standards
$ode Structure
%etrics
Static Testing
Re&'ie or Second loo#
Systematic e(amination of
Softare ) $ode ) Documents )
"nterfaces
to
* Find defects
* +ain understanding
* Discuss & decide on "est choice of
solution
Static Testing
"nformal Revie

, -eview without following any de$ned


%formal& procedures

!o documentation

!o prior preparation for the reviewers

.uic' & inexpensive way of deriving


"ene$t
Eg: Pair Programming
Static Testing
Wal#through

,uthor led presentation

,uthor systematically guiding


reviewers through his wor'

-eviewers & participants +ain


understanding

-eviewers need to "e familiar with the


topic

Some level of documentation is


maintained
Eg: Knowledge Transfer sessions (KT),
Dry Runs, Scenarios
Static Testing
Technical Revie

Discussion on Technical issues /


pro"lems

Discussion on possi"le solutions and


decision "y consensus

-eview leader %Moderator& is present

,uthor can not "e the -eview leader

!o Management participation

Documentation is maintained
Static Testing
Formal Revie ) "nspection

Formal review follows a formal &


de$ned process of review

#t involves six phases


Static Testing
Formal Revie ) "nspection
phases
*+ ,lanning
-+ .ic#&o/
0+ "ndividual ,reparation
1+ Revie %eeting
2+ Reor#
3+ Follo&up
Static Testing
,lanning

Selection of personnel
*
Moderator
*
-eviewers / #nspectors

Selection of -oles for -eviewers

De$ning Entry / Exit criteria

De$ning -eview o"/ective


Static Testing
,lanning

Moderator 0hec's for Entry criteria


Ex: i) after 3 minutes of c!ec"ing no more t!an 3
ma#or defects are found on a single $age
ii) T!e document to %e re&iewed is a&aila%le
wit! line num%ers'
iii) References needed for ins$ection are sta%le
and a&aila%le'
i&) (ut!or of t!e document is ready to in&ol&e
wit! re&iew team'
Static Testing
.ic# 4/

, formal meeting of all concerned


with #nspection

Documents distri"uted

-oles explained

-eview o"/ectives are explained


Static Testing
.ic# 4/

-eview o"/ectives
Ex: i) does the design ful$lls the reuirements
ii) com$liance to coding standards, naming
con&entions etc
iii& maintaina"ility and testa"ility
Static Testing
"ndividual ,reparation

Each of the reviewers must spend


time in analy1ing the document
under review

Points of con2ict( issues( uestions &


comments to "e noted

, list is compiled
Static Testing
Revie %eeting

3usiness li'e meeting

Discussion is held on the list of


issues identi$ed "y each of the
reviewer

,uthor participates and provides


clari$cation

#f necessary ,uthor agrees to ma'e


modi$cations

Moderator ensures discussion is


focused

Scri"e / -ecorder records the details


of discussion
Static Testing
Reor#

Modi$cation / corrections are


implemented for the agreed issues "y
the ,uthor

,uthor should follow change control


to trace the documents for follow*up
Static Testing
Follo&up

Moderator veri$es whether the


corrections have "een achieved and
correctly achieved

Moderator chec's for ful$llment of


the exit criteria

Moderator collects metrics related to


#nspection
Static Testing
,articipants in a Formal revie
are:

Moderator

,uthor

Scri"e

-eviewers and

Manager
Static Testing
Moderator4
Moderator leads the review process
Moderator ensures discussion is focused
Moderator ensures that all reviewers
participate e5ectively in review meeting
Moderator veri$es whether or not the
reviewers are adeuately prepared on
the documents "efore the review
meeting
Moderator performs the entry chec' and
the follow*up on the rewor'
Static Testing
,uthor4
,s the writer of the document he/she
should learn as much as possi"le to
improve the uality of the documents
0larify unclear areas to the reviewers
6nderstand the defects found
#mplement agreed corrections
Static Testing
Scri"e 4
The scri"e has to record details of
discussion during review meeting and
also note defects identi$ed
Develops 78ist of 0orrections9( Minutes of
Meeting etc
-eviewers 4
0hec's for defects in the documents
under review
Static Testing
Manager4
Doesn9t participate in a review process
unless Management documents are
"eing reviewed
,llocate time & resources in pro/ect
schedules
#nvolves in selection of Moderator
Static Testing
Factors contri"uting to the success of
-eviews

-eview must have clear o"/ective

Defects found must "e welcomed

Proper personnel must "e involved with


reviews

Proper level of review must "e selected

6se of 0hec' list & -ole*play must "e


encouraged

,deuate resources & time must "e


provided

You might also like