Scribd
Upload
12 views14 pages

STM Assignment-1

The document discusses path testing, a white-box testing technique aimed at identifying logical errors and unreachable code by analyzing program flow. It emphasizes the importance of independent paths and transaction flow testing, detailing various testing methodologies such as statement coverage, branch coverage, and data flow testing. Additionally, it explains the bug lifecycle and differentiates between testing and debugging processes.

Uploaded by

truparanicse
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
12 views14 pages

STM Assignment-1

The document discusses path testing, a white-box testing technique aimed at identifying logical errors and unreachable code by analyzing program flow. It emphasizes the importance of independent paths and transaction flow testing, detailing various testing methodologies such as statement coverage, branch coverage, and data flow testing. Additionally, it explains the bug lifecycle and differentiates between testing and debugging processes.

Uploaded by

truparanicse
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
Discuss abou PAH fasting ard its Exomple. Path Teskirg js a white —ox testing fecbnique, “" om test Cores ave designed to execeete alt fale Independen b paths of programs Tt focuses on the legecd Plow of ~the progrom. onc enaneS that every Stakemenle and dleasion iS Aesteh — at Leuk ore ~The main aim 0& —path esting is to identify logical jncorvect Conditions ard unvecthable code by ovalyzing & the SFlujore. eNvOrS | | fRe infernal shuckare Hi control Pleo Groph (cPo)— | A gpophical vepresentation oP he pypom cahere Nodes Fepresent Statement — oe Links, * Edges Yeptesent the Stow & control. | 12. Lodependent Paths: [7s Ordependent path 5 a pat “ough the Progra thot | introducet at leaut one new edge and hax nok been | executeck befoce, (3+ Cyelonertic Complety. | a determines the novof Tnclependlent pos | | yen iA Oe V(@) = E-nrQ where, E = noch Edges N= wor of pedey Steps do inveve in path tating 1 Understand the propromn legic 2 Dow the conbol tow gpaph B+ Coteetate — Cyclomatic Complexity 4 Taentify all Srokspent paths S Deng fest coves for each pathy §& Gecaute fest ues ond evaluate vesults | Gomple: — | # (a >b) c=at, eke ceb-a; Independent paths : pth (2 o>b> cx a-b Poke: ach» C= b-a Test ses: Tet case ie a zg, be 3 Tat (3€ 2! 123, b=¢ «d i ; Both patty ore —execobe, ensuring comptefe posh rote tb)} pereribe Sashumentation cern: Panyaction Poco faring i 0 Sofluore Testing techneue we fo fest the Sequence of — cperationd tha otese bn ow See es important concepls Used in dransactton Pheo piste, axe Srshumentoltom sensitizahon. Sensitization in Trantackin Plow | Bikaenibin = Ee svefers do the. pees of taserting additional cele or Statements into the software fo monitor and yeord the exemkon of transaction pathy ae ras Pe pese of Tstrumentation :— > To beck which fronsaction paths are evecated, fT measure test coverage, F? Te Berks onued or missing -transachion flows. ie fe eects exor In frasek ton Sequences , | Sensifizakion 1 a the process of sdecting oppopriate input date. so | that specific -troniaction path is aeheatecl and \ teecuted! dliring faking, | Pepe OF Sensifizations 21 ensure thot the intended transachimy poth S evcuted! J To validate fot, vatid and involiol fronsachion flocs > To achieve complete tronsackin flow coverage, 2a) | Differentiate behween Testing and — Debugging, a Debugging i of lle Testing IS the process of I debugeig hab “fxn the Hf executing 0 progam fo Bnd — | TAnltying cong fi , Gro OF detects, 7: ° lu TO detect failure and defects inthe sofware. eno [g. To remove the canue of flere and comect the code 3+ Usually perfamed by tates 3. Usually performed by OF 8A enginees developers [ prgpammes. U- Foray on verifying anol 4. ous on aralyping code. Validating the Softwore behavior. logic ord fang gues S+ Et iS & planned ond 5 R18 diagnostic and Spstemotic ockeity comective outrty. preluces bug report [failure |. prdlates conected Coole indexmodion A. Test Cases test. scripts, 4. Dduggers bogs, beak points | cuutomateon tools. [PE cools & can be done of cay 1® Done oflo estng identifes ofage of olevelopanen¢ ja defect. | Tahing models provide | development: phe. > Cath phase must be next, 2) V—model (verficatron Dewuibe models for tala, | 0 — ghuckued! —freame coook wthat~ defines hen, how) ancl wha ype OF feng odtivities | Should be pefomed lsing the softwore Development hfe. | Cycle (sore) these models hep ia innproving oftware tality by iategraking tasting with development. | teaberfatl Tatig models - I> Tasting is performed affer the Complefiony of the Complefed hefose moving to the Manoge but at, : é a drat, boa, ye bu © defect deledion 3s a major and validods nena) > An adension P the — wuaterfatt model. p> Teshing activities cue > Each development phos planed Fn poralle) with development hod Covrespordling testing phoue. (3: Troemental Testing model:~ [> software ig developed ant feted in Small increments > Each increment addy | ested laepend ety P> Easter $0 bate gc | new fechinality anh ¢5 cts Onl Seprents touly devon 4 Us Agile Testing model +— / + ‘Testing tS Continuous — ancl Nea ecalontt > Perfomed alonguide devdopment shor ae rk > Emphasizes ceuhomer collabaration ond 9M Redback. S* Spiral Testing Models— > combines iterative development with visk analysis ~ Faking \ perfamed at evey spisal leep. > suthable Poe lorges high isk project. 3a) cloasity the Different —types of Bugs anol Explain, A bug is an enor, flow ov foul inc softwore applitation that cause. it to produce incorrect gy | Onerpected — yesults Bugs can be dbsified bored on their nodure , Come anol impel. (. -funckronal Bugg. > cumy when “the software does not to requirements, > Comred by & logical Bugs ? Gud by perfom Ocarcking incowect or missing Hacky incorrect Logic OF —alguithin implemeatahion > PepaM yung but ga wrong output, 3° Perfomance Bugs; > affect the Spee, Yep ime « under heany loa oy to ‘yesource — otcurs us tog & "ge date. ab) u Security Bugs: > Vulrerabikies tho can leod 40 cnouthorzed — actes ov dota branches. > Vey Critical in Aglare, S Usobility Bugs > Affect a aan and ese oF we > aterfoce ty cafusion oy hare Related to laysut » alignment, colors ov fmt 72 Do not aPfect functionality but impact Oppeovante, ED Thtegratron Bogs; > Oceay when moduler interact Incorrectly — With eochy other, Stale — and Explain Transaction Plow past uf fechniques. TAT 15 a black box — testing technique, " in which Hest Coses ore derived Prom the Lronsackion Plow diagrams of the system. St eases on Verfying — uthether different user tronsacton Pow comectly through —yantowy Septem Components, AH Hronsoction ts a Sequence of Operation, that vepresents Gmplete —_ waer activity tach oa login, monty strontfey ov Plocing ON order. Transaction, Ltow ‘Vesting Tedniques, > Dransaction -Ptow Diogram —Avalipis > valid — Transcuthion, “Teskinoy Drveitid “Wransackion Tasting “Vrontoction posh Coverage p> Weensaction — comlbbinaté on, “Vetting. > Enoe -Hoadling — anch Recovery lata: Advertage »— > Debecks nkespotion exor > Ensure towvect process flow. [data Plow testing focser on how Variable gre defined. cae andl killed progiom « IQ. Date movement and Vanable we, s+ Data flow Graph | To deect dota elated defeds Such 03 uninitialized oy unured |] Variable, s+ white-boy testing |s- At definition, ay upes, +f] | patty. undefined Variable ‘ncoweet Noriable Usage, improper date par | Voriaule Whe eye. i Baka —intersive applicabeons | tv. Bhecking whether | Voable % used bore Sritializati on Comparision falar alata folag 5 More Complex die fp tracking | ord poh Pbuo, path Flow testing 1 poth Plow fasting focuses on enecuting —dlfferent control Plow paths iN ol Program. 9. Control structere ond erecetfion pathy. 3+ contol Flow Graph, & To detect begic ond dleaision = velated clefects s: white Rp 6 Stakement Gvecge , Brarch Coverage, Path coveragy ¢, F Treorret conditions | missing patty logte enor - | |g con be Compler due fo | Select Transaction paths > Design Tet taser > FKeete Test cores and fix Debects. > Aralipts Result Bample:~ AT cash withdrawal Tronsoction : withdraw cash | steps :~ b Shek Atm cod 2. ener PW 3: Sdect * wwithdrav | uw Erher amount > Cah dipersed Transaction paths: es oe Cowect pin > valid amount — cash ae >Tnvolid path= Tsort cord > wo WY —> Tronsaction Concetted,

You might also like