Please enable JavaScript.
Coggle requires JavaScript to display documents.
C5 : Static Test Technique (Static Analysis (Element of a static analyser,…
C5 : Static Test Technique
Static vs Dynamic (compare)
Dynamic
Testing that involves the execution of the software of the component or system
Documentation relating to test objects is created in a construction phase and used as a test basis
Method
Black box
White box
Static
Testing of a component or system at requirements or implementation level without execution of any software
Method
Tool support : Static analysis
Manual : Review
The test object will be
verified
against a document of a prior construction phase
Static Test
Analysis of a
test object
(mostly documents) via intensive observation
Objective
Detection of faults/defects in an artifact
Goals
Defect prevention
Review vs Static Analysis (compare)
Review
Use human analysis and thinking capabilities
to test and evaluate work products
Done by one or more people
Manual observation of the test object
Any software work product can be reviewed
Static Analysis
Observation of the test object via tool support
Automated testing by means of tool support against predefined rules
Compiler
Used only for documents with a formal structure
Source code
UML Diagrams
Review
Why reviews?
Effective defects detecting
Gaining understanding of documentation
Satisfying requirement or compliance
Roles & Responsibility
Moderator
Leads the review
Planning the review
Run the meeting
Reviewer
Checkers or inspector
Represent different perspectives and roles in the review process
Scribe
Documents all the issues, problems and open points
Manager
Determine if the review objectives had been met
Decide on the execution of reviews
Allocates time in project schedules
Author
The person responsible for the document(s) reviewed
Types of Review
Informal Review
No formal process
Objectives
Inexpensive way to get some benefits
Technical Review
May vary (formal - informal)
Objectives
discuss, make decisions, evaluate alternatives, find defects, solve technical
Walk-through
May vary (formal - informal)
Objectives
learning, gaining understanding, defect finding
Inspection
Formal
Objectives
find defects
TIps
Review the product, not the people
Finding defects, not fixing it
Review the result of review
Success Factors
Have a clear predefined objective.
Involved the right people
Defects found are welcomed, and expressed objectively.
Emphasis on learning and process improvement
Static Analysis
Objectives
To find defects or error-prone areas in a document
Example of tools
Spell-checker
Compiler
Document adhere to formal structure
Software architecture
Software designs
Technical specifications
Element of a static analyser
compiler as static analyser
control flow analysis
data flow analysis
calculation of metrics
source code analyser
Defect discovered
Referencing a variable with an undefined value
Unreachable (dead) code
Missing and erroneous logic (potentially infinite loops)
Programming standards violations
Benefits
Early detection of defects prior to the test execution
Early warning of critical aspects in code or design
Detecting of dependencies and inconsistencies in software models