Page
Auomation csthing.
. Basics of SoftwareTesting
Softwarc testng
js_working properl,
Checking whether [Link]
Satisfs the customets needpr_nas_so.me em erDrs
o
bugs
Benefits
0 SecLEits-
Cost etfective
Custbmer Satistacion
Hinding ertors ahd bugs
Pindples of
0 Optimal rsting
Pareto principle Lcan be known as 80:20 rules)
Revise ond evicu
indinq_defects and specifying Customers'need.
est carly
Meeing Customers'need.
Defects that ar present.
Obiecttves of Software Testing
0 [Link] that are present in the softwarc
preventit
lo increas.e the Contidence in the gas(Quality o
Sottwaure
To ensure that the [Link] oactually mcets Hhe
Customers' tequrement
To provide thc customer_witb Quality poduct D-
develope Confidence tor Company
Buq
Tnformal name of defect.
Code doesnt give any error or runs well but
Qives nexpected results
Error
Mistakes of developers in Suntaxof code
Syrd-ax may Vary trom lanquage to Janguage
Fundamcntal test processes
1) Planning
*First Stage ot Hestingproces
*Duadion date, risk SCDpeabiectives are
defined
a Monitor
Second stage ct festing process
carried
Determine the steps ór process o be
aut in testing.
3:Anale2e
Analyze exactlywhat to test
T is done on test basis.
4 Design defined.
* How we have o test the madwe is
To decide theype aftesting
Page
5Tmplement
Checking _whether the hardware and softuoare
we ae usinq. for testing are Capable off doing
doina it
for the type which we've choasentor testihg_ar
Or
not
sExecuion
Actually dealing tuith pmblems
*Executing testing pmcess
)Campletion
*Last 6taqe of testin [Link]
*Task is completed
Summatize he testinq
*teneraBes he recommendaion.
Qualihy Assurance
Quality Paramete ts fortabilhy
funcionalih-
Not [Link] hot pathular
cffhcicdgy-
team is assigned tor qualihy AtcuracH
Speclal team warks an ualiyassuardne
Co ndio
Date
Page
Quality Assurance Quality Co ntro.
Preteqisite Postrequisite
Process based PAoduct based
documentaion veritication Product validation
and all types of Partabilits validachion,
vepitications and all y pes of
Validations
Stahc tesing toals
* doesnt require ony input/auctput
Componets
Plow ancalyze
Path test
Coverage analyzer
Tntetace analyzet-
Quality Assurance
Metbed of making thc Sotware application with
finally
Tess defects and mistakes whenit is
relea sed to the end
usSe
apprnaches, tech niqucs
An achivit hat enSLres_FHe
ppject ac
methods proCess designed for
implemented CorIectly.
Coopleted betore qualhy_Contw.
clASSMALte
Date
Page
Quality control
* Process that is used to ensute that 4he approaches
techniques, [Link], [Link] designed
in he praject arc tolloainq CotrecHy
Operates verity fhat the application meet
the quality Gtandards
Focuseson testbing at end pmducts quality.
TEstinq
Process of uerRinq validahinq whether a
Softwaie or application is bug-reemeets he
technicalrequlrements as quided bu its dasigp
development,mcets he uset tequrehments
cfectively efhcientiy by [Link] aul the
exceptional ¢ boundany Cases
Testing
Veritication Validadion
Set of tasksthaf enures
hat the. softuoore DHferentset af tasks that
engures thad softwan has been
Cortectly implemended bullt js traceable tn_customer
hequattMents
elssmate
Date
Page
Static testing
Mcthod whichis performed to check thc [Link] in
hes Software [Link] actually executang the codeot
the 8oftware application
Petor med in early stage at development
o aoid etrors as it dg eaiicr fo Hnd Sources
of tailues and it Can be Hxed eaily
k_Errors that can't he fbund wing dynamic testing.
Can be found bs_Stahc tsting
Dunamic testinq
Testing which is performed to analyze the
dynamic behaiiour of the code
Includes the testing of the software for the
inputyalues ah.d output yaluer that ae analyzed.
Static Softuuare Dunamic Software
testing
teshng
In early stage of Software Latu staqe of Saftware
Whole code isht exccuted Whale ndeis executed
Prerents the defects s)finds d fixes the defects
Perfermed beforr code deploy Performed attcrcode deplay
SCost is Jess 5Cast is high
en 972InvnJves chccklist Thvolres fest cases
ncludes walkthroug hs. ) Includes functianal hot
Codc revie, inSpection funchional testings..
2Takes shoter time 8) takesdongerime
9 S0 statument coehage-
9100, statemenft covcrag
1o Ex 1 Ex
Valjdahion.
Verificatian
Date
Page
Advantages a n d Disadvantages
Advantages
Speed
a Eficicny
3 Aceuracy Precision
Resource reduchion
S) Simulatian emulHon
[Link]
)Reduce time cf tcshng-
8Tmprniethe bugs Hndinq
Deliver the 9ualits satuare prnduct
1o) AJlow fo run ests many imes Luith diferent-daa
11) Gething moreimc for test planning
l)Sareesources or educe [Link]
*Disad vantages
1 Tt is mare expensiie to [Link]
[Link] are bigger that manual testing
o Manual test can be verytime Consu mip
3Youcannat Cutomate renthing
4 Can't rely on t alwoys
Autbmaed testin is tequired uhen 04Lwant
to tun the Sameest Cases across
mulipc
machines at Same me
clSSMAte
Date
Page
Automation testing un
0 Easy asseution
Reusable stepsS
d
OEnvironment Support
e Ease af usc
Training cost
0 Objecth identification.
Lmage
ds Frror ecoUey
ScripdHnq Janguage
elASSMAte
Date
Page
9 Jupes of Soflware leshng-
lypesof Softw ate testing
JWhite Box Testing Softoate Can be obseved
The intetnal mechanis.m ot
ttansparent9ass,Or
OTt is also_knotwn as Clear,
Structural tasthing
White boxtesting
Stuctir-tcsHng- Dyhamictestinq
Structural testing
Desk Teshnq Code [Link]-
Code lakthrnug Code cove rage
Code [Link] Code. complexities
Stadement coverage lath Covemge Condithon Performance-
CoVcage- Coverage
nate classMAte
Dafe
Page
Desk testing for tesinq
0The &0ftuwate is devided into modules
frster
Each [Link] is ttsted by individual
Documentation for ercry sinqle thingis to be
Or maintained
Cade walkthrnugh
0 Lor Every teammaBe checks or tests the pipgram
t is [Link] activity-
Suggestions ate given p each ather
Code [Link]
eFer executed.
restina est cases_ate creacte ol
Dynamic teshng
es. Changes Can be done, to Tectih the code
Cnde functionalihs
rmante
erage
Code coVerage
0Statement coraqe
Percentage ot non-executable 6tatemnents af
Code
formLda
Stalementkr expeiencedx 100
6tatemenkr present
Date
po9e
Patb coverage
Date
Page
Test cases
fields
roject name
Madulename
Created dace
Createdby
Test [Link] Td
Test Scehario Description
Test Case TD
Test Case Descipton
Pre Condition
Post condition
Expectrd Output
Hctual outptut
Status
Revie Date
Review by
Comments
elassMate
Date
Page
HZu zuF
clASSMAte
Date
( Page
Start
Taput hum
num 2)
Y e s
Numbe ts
ecD
Number is
add
Peint autp ut
End
Flow paths
Path 1 1 3 4S
Path 2 19 6 S
Black box testinq
*Tosting the functionality of sottware
No need to test or tous internal Shuoture of Codt
Ahy to do
End user perspecHve
) documentatlon at equilemenf
3)State and impliedrequremenks handling
handling valid and inualid inpuds.
hen todo ?
Itis done aHer dercloprment of Sottware and
before tbe deploument of final product, exactlyaft
completion of whitebox tesHag
How to doP
Black bax tesinq is done in the follawinq ways.
1RequredmentBased1esting
Pasitive and Negaiveesthng
3Boundary Value Analysis
4 Descislon Tables
sEquivalent farHioning
6) User Do cumentaion Testing
Rcquirement based tesHng
*Kequirement testinq is donebased an the SR
TRs Testinq Requirement SpeciPicatton ) documentai ation
js maintain ed
Date
Page
racabilihy
*Using the SRS and RS, Requiremcnt
Matrix (RTM)
Require oent Traceability Machx
Fhdds(Raramctes Used
1 [Link]
RequwirementIdentiie
Requement Descnipton
4)Testcase Tdenthifier
5) Test Case Description
Priatity Higb, Medium, Low)
Total case humbers
8 Total Pass
9Totalfail
10)Total percentage
Sr-No ReaTRe-De TC d Tcpes PrioHty Total Cast N. fEcetage.
Total PassTotolfail Prcentage
BRO ky 1os High
CJockwise
tUalok"|
clASSMAte
Dafe
Page
fositive and Negaivetesting
*Lhecking wbethe the ee actual ouput expecte a
Ourput Qre_matthing or not while giuing fhe positiVe
hegctivc Output-
C
elasSMate
Date
Poge
2Bdundany Value Anal
* I is used when defects i prngram ate be found
Out
Defects are found bascdon heZmajor componenks 04
tollows
Conditon 6ituation_Ot the Scenano.
i
i Boundaries imits.
testqases
ipata9eteks Such ag
*I is done using thc
minimum value Cmin value
maaimum Value Cmaa Value)
mint1
4 max-2
Page
Descision Tables
*Used when input_validity is to be checked and
this-
further [Link] to be made based on
are
ate made depending_upon the actiohs P
*_Descisians
Condition
For example
Usemome
[Link] Qdmin
Passuord admin@i28
ondiHHon Acion
Fmoil has
T T
CASSMAte
Date
page
User Documentahon Testing.
User manuals are written and tested
The documents should be in keadable and uSerftie nd
ftiend
tormat
Includes terms and conditions, LUSer manunls that
CDnsists a teps and how-to' to use the Sofba
Libray manouqement ssStem
Reqister USer Uogin)
LSetname admin
paasuord admin@L2g
Condition Achion
(L8ername Dalswoe
Allaw access
EnterCo reat pasword
Page
Libbraay Management stem
Expected
Register ed Unde: Fees
Output
uset boak limit paid
Succestully Laggeal to
True ruc ruc Pay fees Aist
True ruc Palse
Lim recachcd
rue [Link] e
Payfees ch
Irue false false
False Irue ue
nvalid
False Ine Palae Lualrd
False falae ruc
Tnlalid
false Palse False
