PART-1 BBT Vs klBT

O
CUNTT-TI 9 4 c eutiva VS dyumi fechrg.
Vali'cd en Vs Vobdal m
aAVs de
unchonBe Us Nen-fncdionsl tai
DYNAM1C TESTING lResngVs Regvein fedina
STA11C TESTING
NFORMAL REVIEWS
STRUCTURAL fUNCTIONAL NON-fUNCTIONAL
FOR MAL REVIEWs TESTING TECTING TESTING
WALk THRDUGHS PERfORMANCE
WHITE -BOx BLACk BOx
ECHNICAL REVIEWS TESTING
TaHan fet sproded, fex Coe JeSTING TESTIN6 LOAD TESTING
TNSPECTION BVT
bBasue palh STRESS TESTING
SMOKE PVOLUME TESTING
SANITY >RECOVERY TESTING
> Combrel Sbiuetut RELIABILITY TESTING
RE-TESTNG
REGRESION TNSTALLATIDN TESTING
EXPLDRATDRY COMPATI61LITY TESTING
AD-HOC CONfIG URATION TESTNG
CEatimt
CowAa SECURITY TESTING
TNTEGRAT 1ON
BAaMh
Cuty SYSTEM TESTINg
>UNIT TESTING
 SoFT l4ARG EMGT NeERTH G
PART-2
ROZE2 SoFTIARE TESTTNG
CUNTT-
lhai Sopweee Teki ug?
Ret 9F erug a Retint to vakdat wkehee se es pvnoaut
m.edts the 5uneu veqiremet the Cujomot nod.
s F Hertig u &dintto Jepe wkeme he acfual
elul mafoher the
9F es tiug i actin4g to eheek wkehe the sF
a in derded ae me
wor
S F ehng e n activitt to n u e ha the slE M
a
9ualit produed od alpo bug feee
brocer f þrgror cuting a
¥ se teng a One

he dofubie ugf.
opplitation with he Indene nding
Hejing a nagative oproack wl pop Ave allude
x SF
eonpruvo oRkde
a dostvuskive eppvook
s E fetng
fei ng mpt poeh ble.
loof. 4eting pt Orkantüre
*No bu9 Cam Ines hat g-PPwter bug feee
7 ucert1
Had apltcoion a breale qra fstugl.eut
afdprodek aln ind
cattruHve
ybuptret e e oppi pHon od
onduh en o eutte

NOTE-Slhvate Tu tug faRT-1 &taw Ayuee ef Tutiug tyke-

 QACAMPUS
The Education Division of CresTech

3.1 Black Box Testing

under
without knowledge of the internawerktmgs of the application
Black Box Testing is testing software testing
as fAnetionaltesting or
iapHt-outputdeiven testing. A
test (AUT). Also known For
the internal workings of the item being tested are not known bythe tester.
technique whereby
on AUT the tester onBy knows the
inputs and what the expected
in a black box test
example, eutputs. The tester does not ever
outeomes sheuld-be and not how the program- arrives at those
of the program other
code and does not need any further knowledge
examine the programming
and the programmer can be independent of
one

For this reason, the tester is

than its specifications. work. This method of test design
biasness toward his own
another, avoiding programmer's system and
of software testing: unit, integration, functional testing,
applicable to all levels
cannot
one
unimplemented
uncover parts of the specification,
thismethod can
acceptance. While
ip.
be sure that all existent paths a r e tested. cug e he modale tgi posgible
obseive the behavi
ImBOT, tku leres Box Testing
The followingthe are types of Black

3.1.1 Build Verification Testing

(BVT
that-the
cach
of tests run onnew build of a produet toveHty
i sa set
verifieatientest test is generaly
A build Build Verification
the test tean.The
buildis send to Any build
build istestable beferethe mainstream functionality of the application.
which exercises the continues on the previous build
a short set of tests,
is rejected, and testing
verification test the verification test). So
builHd
that fails the build build that has passed
(provided there has
been at least o n e ceneeived. Build
is done-every-time a new-build is
regression that
know right away if there is a
serious
Veriticationtests area type of let developers
because they that is
Verification tests are important time and
frustration testing
test team wasted
they s a v e the
problem with the build, and
time a new build is taken. too muth dap)
every eud getiug
done

t o r a gen ol boooek)
Smoke Testing (shallau and wide
3.1.2
accepting a
the build is released or by testers before
developers before method tor
Smoketesting is done by smoke testing is the most cost effective
code reviews, test generally
build for further testing. After software. In software
engineering, a smoke
identifyingand fixing defects in
computer
created or repaired
be applied to a newly
that builds the final
can
collection of tests
consists of a
the automated system that
Sometimes the tests are performed by before the changes
program. code changes
In this sense a smoke test is the process of validating
software,
collection.
official source code
are checked into the larger product's

www.gacampus.comn
Your one stop testing portall 28
 Iclrolp Swaub-In
16rollo Aviseh- Iro

QACAMPUS R
The Education Division of CresTech

This is a "shallow and wide" approach to the application. The tester "touches" all areas of the
application without getting too deep, looking for answers to basic questions like, "Can I launch
the test item at all?", "Does it
open to a window?", "Do the buttons on the window do things?".
The purpose is to determine whether
or not the
application is so badly broken that testing
functionality in detailed way is unnecessary.. These
a more
written tests can either be performed
manually or using an automated tool. When automated tools are used, the tests are often initiated
by the same process that generates the build itself. This is sometimes referred to as "rattle"
testing as in "ifI shakeit does itrattle?"
To summaries smoke testing is:

In software industry, smoke testing is shallow and wide approach

a
whereby all areas of
theapplication without getting into too deep, is tested.
Asmoke test is scripted, either using a written set of tests or an automated test

A Smoke test is designed to touch every part of the application in a cursory way. It's
shallowand wide.
Smoketesting is conducted to ensure whether the most crucial functions of a program are
working, but not bothering with finer details.
Huuch Re esta bnt o musk o Previau be la)
3.1.3 Sanity Testing (nattp nd dep opþoach)
deep
Sanity testing is a quick, and atesting performed whenever a cursory testing is
Sufticient to prove the application is functioning according to specifications. If the smoke test
fails,itisimpossiblefo conductasanitýtest. The idealsanitytestexercisesthe smallestsubsetof
applicationfunctions needed to determine whether the application logicis generally functional
and correct (for example, an interest rate calculation for a financial application). Ifthe sanity test
fails,it is not reasonableto attempt more rigorous testing.Both sanity tests and smoke tests are
ways to avoid wasting time and effort by quickly determining whether an application is too
flawed to merit any rigorous testing.

lo summaries:

A sanity test is a-narow Fegresston-test that focuses on one or a few areas of

functionality. Sanity testing is usually narrow and deep.
A sanity test is usually unscripted. (Not obvious)

A Sanity test is used to determine a small section oftheapplication isstill working after a
minor change.
www.gacampus.com
Your one stop testing portal!
29
 the epplítad on e k incuelt
e e ek n e c
hCAMPUseaduuar agnmet bokohknd ole
Cal d got The Education Divjsion of
CresTech

3 4Het CPvdentd ePPwh in.

3.1.4 User Interface Testing (leok end sel

the user interface to itfollows accepted

ensure that
User-interface testing is the testing of referred to as-graphicaluser
is often
standardsand meets its requirements. User-interface testing
i.e. testing the interface extensions of the application to the
nterfaee GUD testng or UI testing how4displays
user. This includes haw theapplicatien
handles keyboard and-meuse input and
teelbars and mere
SCreen text, mages, buttens, menus, dialeg bexes,ieens, n . hou
To tei he jet end ynoel d dte opPl co
3.1.5 Usability Testing (8koTtoul Kot+Condrpl
The aim is observe peopleusing the product
to
Usability testing is a black-box testing technique.
to discover errors. Usability testing generally involves
measuring how wellrespond in four areas:
etficiency, accuracy, recall, and emotional response.
basic
Performance How much time, and how many steps, are required for people to complete
tasks? (For example. find something to buy,
create a new account, and order the item.)
fatal recoverable
people make? (And were they
or
did
Accuracy How many mistakes
with the right information?)

nuch does the person remember afterwards or after periods of non-use?

Recall--How
feel about the tasks completed? !s the person
Emolional responseHow does the person
confident,, stressed? Would the user reçommend ethis system to a friend?
loe w dh actusl
e
e a Hhat t i e k c
eeproA
3.1.6 Integration Testüng
One ofthe most difficult aspectsof software development is the integration and testing oflargc
untested sub-systems. The integrated system frequently fails it significant and mysterious ways,
anditis difficult to fix it.ntegration' testing exercises several units that have been combined to
form a module, subsystem, or system. Integration testing focuses on the interfaces between units,

tomake suretheunits work togetherann nuce ng bropesly with ach otheL

here arethree main approaches to integration testing:top-down, bottom-up and 'big bang. Top-
down combines, tests, and debugs top-level routinesthat become thetest harness' or 'scaffolding'
for lower-level units.
Bottom-up combines and tests low-level units into progressively larger
modules and subsystems.
'Big bang testingis, unfortunately, the prevalent integration test
method. This is waiting for all the module units to be complete before tryingthem out together.

www.gacampus.com
Yourone stop testing
portal
30
 QACAMPUS
The Education Division of CresTech

3.1.7 Compatibility Testing (o Corigurebn efiug

conducted the application to evaluate the
Compatibility testing, part of software is testing
on

environment may contain some or all

environment. Computing
application's with the computing
of the below mentioned elements: (0. 9, BewSek, dadelose, tile, 'Lmoqt
Database (Oracle, Sybase, DB2, etc.)
.Other System Software (Web server, networking/ messaging tool, etc.)

Browser compatibility (Firefox, Netscape, Internet Explorer, Safari,etc.)

3.1.8 Retesting Cmodi el baild)

reported in the previous
Retesting is a type of testing in which the tester checks that the defects
build have been fixed. This requires re-running thefailed test casesS
defects have been reported in build 1.2. These 10 defects will
onsider example in which 10
an
the new build
When all the ten defects have been fixed,
be assigned to developers for fixing.
have really been fixed. This is
with the changes will be retested to verify that the defects
retesting.

3.1.9 Regression Testing medifad bild

which we check for new bugs introduced due
Regression testing is a type of software testing in
made inthe previous build.
tofixing thereported bugs or changes
earlier build have been fixed i.e. we re-test. This
Here we also check that the bugs reported in the
Regression testing is often accomplished through
the
requires re-running the failed test cases.of
product and system tests. Regression testing is an
construction, execution and analysis that
necessary activity pertormed onmoditied software to provide confidence
expensive but
other system components.
changes are correct and do not adversely affect w i h u t planiug doumetehn

D No ste Cole etc wmkeu

3.1.10 Ad-Hoc Testing
dane uwhen Joy F e hu lePrug
performed without planning and
Ad hoc testing is a commonly used term for software testing
to be run only once, unless a defect is discovered, It is
documentation. The tests are intended
tester seeks to find bugs with any means that seem
performed with improvisation; the to other types of testing
often used as a complement
is most
appropriate. Ad hoc testing
www.gacampus.com

Yqur one stop testing portal!

(iv Tn oolhsc dedru oug po 1cpd
Bug Stport9 mot vciwed
 6ereheny dehA dptl m 8llad eli Te Cek ase
watlont die colet e e bug eteon(suutepo
u
(9 ET puprmed b rpc2in tolerer. Th Heling dependon
n odvonce.
G0g npagOockoTesd cole pe not delgned
Bug 3or eodec
ACAMPUS
T te-tug doe hen theu The Education Division of CresTech

3.1.11 Exploratory
Exploratory Testing et Cel vepar and bug Sporf
lesune as of ecviewed
Exploratory testing is an approach in software testing that is concisely described as simultaneous
learning, test design and test execution. Cem Kaner, who coined the term in 1983, now defines
exploratory testing as "a style of software testing that emphasizes the personal freedom and
responsibility of the individual tester to continualy optimize the quality of his/her work by
treating test-related learning, test design, test execution, and test result interpretation as mutually
supportive activities that run in parallel throughout the project.

While the software is being tested, the tester learns things that together with experience and

creativity generates new good tests to run. Exploratory testing often thought of as a black box
testing technique.
Exploratory testing seeks to find out how the software actually works, and to ask questions about
how it will handle difficult and easy cases. The testing is dependent on the tester's skill of
inventing test cases and finding defects. The more the tester knows about the product and
different test methods, the better the testing will be.

To further explain. comparison can be made of freestyle exploratory testing to the antithesis
scriptedtesting, whicn basically means that test cases are designed in advance, including steps toC
the
reproduce and expected results. These tests are later performed by a tester who compares
actual result with the expected.
When performing exploratory testing, there are no exact expected results: it is the tester that

decides what will be verified, critically investigating the correctness ofthe result.
In reality, testing almost always is a combination of exploratory and scripted testing, but with a

tendency towards either one, depending on context. The documentation of exploratory testing
ranges from documenting all tests performed to just documenting the bugs.

3.1.12 Performance Testing

In software engineering, performance testing is testing that is performed, Performance testing is
a subset of Performance enginecring, an emerging computer science practice which strives t0
build performance into the design and architecture of a system, prior to the onset ofactualcoding
effort.

Pertormance testing can serve different purposes. It can demonstrate that the system meets
pertormance criteria. It can compare two systems to find which performs better. Or it can
measure what parts of the system or workload cause the system to perform badly. In the
diagnostic case, software engineers use tools such as profilers to measure what parts of a device
www.gacampus.com
Your one stop testing portall
31-13 Spleun tegting 32

3.1 14 Ur Acceptonce Ttng (vAT

h Hedeg eltg ivetug He Cere o g deleil

ACAMPUS
CresTech
he Education Division of

Assignment
1. Differentiate between Retesting and Regression testing?

2. Differentiate between Load and Stress testing?2

3. Which is the first type of testing performed by testers?

When a build is ready give the order of types of testing that will be performed?

5. 1s the user involved in testing? If so in which type of testing?

6. What are the measurable parameters in Perfomance testing?

e Het9 tevddo
on a
Certet
156 Syren Herfrugs.T won woreg Cored h
neeqded yem te ralte 4R
4 ead e reaneti
ST we f e ah
PEcoh orn CABT

compA
ComPiled ond
ene cuteel
u
die
2Ln UT urt Yha s pejoym
vakdete 4het e h
I pupofe uto tRe cole
e
as dese l ovciyinefetiug
doh9 we lea lecti9 Iotf
In f ooli dionel tceptim
dno
C o m d r d y u t s e ,

olgonthn
dEbth, cecug probar A olgonlm
eSRhorolivg e c 0aco
et e odle n used
we tli e
6In uT,

0A}a leuh Befo fehu Cu me

BCT
con
1 9 UAT UAT thionbekave
nd wW.acampus.com ad he fpl
UAT oniuse Your one stop testing portall
orped ed b
d uel, de odo
dho dovelsf o9 in FRcion Cfme o
o

pha,duiug
3)Aloeelsp o b
wen ide cudvmuet Re eed le to gef
J olve b e
d e h deh busk fo m namwn me o ets
 CresTech
ETACAMPUS The Education Division of

4
Key Concepts Chapter
4.1 White Box Testing
4.1.1 Basis Path Testing
4.1.1.1 Flow Graph
4.1.1.2 Flow Graph Symbols
4.1.1.3 Cyclomatic Complexity

4.1.2. Coverage
4.1.2.1 Statement Coverage
4.1.2.2 Branch Coverage
oUs
4.1.3 Control Structure Testing
4.1.3.1 Loop Testing
4.1.3.2 Relational Operators
4.1.3.3 Boolean Operator

www.gacampus.com
Your one
stop testing portal
36