Types of Testing

• V Model
• Testing Phases
• Static Testing
– Reviews
– Inspection
– Walkthrough
– Metrics
• Dynamic Testing
– Unit
– Integration
– System
– Regression
 SDLC and V Model
• There are some distinct test phases that
take place in each of the software life cycle
activity

• It is easier to visualize through the famous

Waterfall model of development and V-
model of testing.

• The V proceeds from left to right, depicting

the basic sequence of development and
testing activities.
 SDLC and V Model
Developed System

Wishes, Ideas,
Concepts

Acceptance Test Plan

Requirements Acceptance
Specification Test cases

System Test Plan

Functional Design System

Test cases
Integration Test Plan Regression
Verification

Detailed Design Integration

Test cases

Unit Test Plan

Program
Specifications Unit Test cases
 V Model

The model is valuable because it highlights the existence

of several levels or phases of testing and depicts the
way each relates to a different development phase.
Why Write Test Cases Before
Coding?
• When adding a new feature or enhancing an existing
solution, writing test cases forces you to think about
what the code is supposed to accomplish.

• You end up with a clean and simple design that does

exactly what you expect it to do.
 Example fpr Triangle
• 3,4,5,6 Four sides
• 646 Three-digit single number
• 3,,4,5 Two commas
• 3 4,5 Missing comma
• 3.14.6,4,5 Two decimal points
• 4,6 Two sides
• 5,5, A Character as a side
• 6, -4,6 Negative number as a side
• -3, -3, -3 All negative numbers Empty input
 Static and Dynamic Testing
W Static Dynamic
H Unit

I B
Reviews Integration
T UAT L
E Walkthrough Desk Check A
System
B Inspection C
O Performance K
X Exploratory B
Volume
O
Recovery X
Installability
Reliability Usability Security
Documentation
Localization Configuration Stress
 Static Testing
• Reviews
Methodical Examination of Software work product
done by peers of producer is called a review
• Review helps in
Early Detection of Defects in SDLC
Emphasize Quality throughout Development
Cost Effective way of finding defects
 Static Testing
Walkthroughs
Code Walkthrough is a set of procedures and error
detection techniques for group reading
• In Walkthrough meeting, three to five people are
involved. Out of the three, one is moderator, the
second one is Secretary who is responsible for
recording all the errors and the third person plays a
role of Tester
 Static Testing
• Walkthrough helps in
 Approach to Solution
 Find omission of requirements
 Style / Concepts Issues
 Detect Defects
 Educate Team Members
 Static Testing
Inspection
• Inspection focuses on the procedures, forms to be
filled out and etc.
• Normally Inspection team will consist of four
members. One of four plays a moderator role and he
is expected to be a competent programmer but he
should not be the author of a program.
 Static Testing
• Inspection Helps in

 Detect Defects
 Conformance to standards/spec
 Requirements Transformation into product
 Static Testing

• Static Testing is more white-box ie. deals with the

nuts and bolts
• Static Testing helps weed out many errors/bugs at an
early stage
• Static Testing is particularly significant in the
Waterfall approach to S/W development
• Static Testing lays strict emphasis on conforming to
specifications.