, I / j ;

I , , I I
( I I , ' I
;
l • I •

{ ,
• I f i ' • I
'
I
.
J ' . I •
l I

.J

I' I I I .,

) I I I ' '
I
I
I )
I

,~ \ \ I ·, ( J I
.I

j I
·, \
 @) Tt~ ~ ~ b ~ ~ to v ~ 0 j- LJ) CU- ~ evl ~ 1

bQ r ~ ) f OJ-h! ~ ltm.oLL.\ilfY\-},
' ° l ~ TQ(((j_'. j '
f,~~ .r< •

~ . ~6r'LoJiYJ
b·hr ~ \JA..tk B01
NW Ct: ~ox

I1
1~MM
Q)
·--
6t~YY\Jmk U>v~
l © t~ v ~
f ~ t i M'V-' ~
I. @ oCtLt'S i.: aY\. ~ @ ~~ Vt>JJW..
a @ ~ h,' (TY\. 4 ~~~
1 ~ MJ.ulipJ-A- U)"Y\.OU +•tCfY' @ ~tALL ~·~~
~~ U V ~
I
&) ['fr~ ~l.U.AM1'
~I l~ k ~ Tt'i'v'~-
! A-~ 1~ ~ TU-Wj
I (D .() OTu.. ~ IN_ tu:t\-ol'Y\.lh Cl\.k" (D .() lrN.- ~ lr\.t, Ul ~
o\JJJ~~ ~(t ~ lAWt's / w_~'~ 'k\~
@) umd.uifw tin,, c>-.. Ufrvt tUf\Aw © ~ . w t l'Y\. \tQJ>J ho/'r\1.-
UY\v L'<-f-~ . ~\J l"I ~ ) ctt.n ~
ttA_o_ ~ ' s l<wu-tt ITT.
© ~ I\, fltU.IJyJ- ruw7 @ Kl L v ~ i~ ~ ruw
h,tttJ'.,. 1L4ltl~ _
€) ~~ 61Ar k 1'llt ~ ~ ©~ o-vr ~ rlt\t ~
- ~ OJ fV\0- p~odtltt ro tLltto - -/u_ ~ pcroct.u.U- \-o l

-- rrY\.0\,,- ¼ _ ~"-

@,£crc-d:i <-& ! / fU lW-»., @J-t.Q_ ~ f IA..l ~ Ovu hLf o~

tlu-0~
® JS\-v'lf' t fM.MAz,, Box
TLMi~
 Black Box Testing White Box Testing
It is a way of softwarE It is a way of testing the
testing in which the software in which the
internal structure or tester has knowledge
the program or the about the internal
code is hidden and structure or the code or
nothing is known the program of the
about it. software.
It is mostly done by It is mostly done by
~
software testers. software developer~
No knowledge of Knowledge of
implementation is implementation is
needed. required.
It can be referred as It is the inner or the
outer or external internal software
software testing. testing.
It is functional test of It is structural test of
the software. the software.
.,.

This testing can be

initiated on the basis This type of testing of
of requirement software is started after
specifications detail design document.
document.
 I
No knowledge of ,, It is mandatory to have
• •
programming is knowledge of
•
required. programming.
It is the behavior
It is the logic testing of
testing of the
the software.
software.
It is applicable to the It is generally applicable
higher levels of to the lower levels of
testing of software. software testing.
It is also called closed It is also called as clear
testing. box testing.
It is least time It is most time
• •
consuming. consuming.
It is not suitable or
It is suitable for
preferred for
algorithm testing.
algorithm testing.
Data domains along
Can be done by trial
with inner or internal
and error ways and
boundaries can be better
methods.
tested.
Example: search Example: by input to
something on google check and verify loops
by using keywords
Types of Black Box
Testing:
Types of White Box
Testing:
• A. Functional

Testing • A. Path Testing

• B. Non-functional • B. Loop Testing

testing

c. Condition testing
• c. Regression
Testing
What is Verification in
Software Testing?
Verification in Software Testing is a process
of checking documents, design, code, and
program in order to check if the software has
been built according to the requirements or not.
The main goal of verification process is to ensure
quality of software application, design,
architecture etc. The verification process
involves activities like reviews, walk-th roughs
and inspection.
What is Validation in
Software Testing?
Validation in Software Engineering is a
dynamic mechanism of testing and validating if
the software product actually meets the exact
needs of the customer or not. The process helps
to ensure that the software fulfills the desired
use in an appropriate environment. The
validation process involves activities like unit
testing, integration testing, system testing and
user acceptance testing.
Verification Validation

• It is a
• The verifying dynamic
process includes mechanism of
checking testing
documents, design, and validating
code, and program the actual
product

• It always
• It does not involve involves
executing the code executing the
code

• It uses
• Verification uses methods like
methods like Black Box
.
reviews, Testing, White
walkthroughs, Box Testing,
inspections, and and non-
desk- checking etc. functional
testing
 • ltchecks
whether the
• Whether the software
software conforms meets the
to specification is requirements
checked and
expectations
of a customer

• It can find
• It finds bugs early in bugs that the
the development verification
cycle process can
not catch

• Target is application
and software
architecture, • Target is an
specification, actual
complete design, product
high level, and
database design etc.
 • With the
• QA team does involvement
verification and of testing
make sure that the team
software is as per validation is
the requirement in executed on
the SRS document. software
code.

• It comes before • It comes after

validation verification