, STEP TOWARDS SUCCESS § 2 £ ; - AKASH’S " is Guru Gobind Singh Indra Prastha University Series a Dd Eo 8 reg e _ SEVENTH SEMESTER [ogee aes Quality | fe - Assurance (ETCS-403) a ‘ ss se xoSYLLABUS EO __—————————— SOFTWARE TESTING AND QUALITY ASSURANCE (ETCS-403) Instructions to Paper Setters: MIN QUEEN NG. 1 should be compulsory and cover the entire syllabus. This question should have objective or short answer type questions. It should be of 25 marks. 2. Apart from Question No, 1, rest of the paper shall consist of four units as per the syllabus. Every unit should have two questions. However, student may be asked to attempt only 1 question from each unit. Each question should be of 12.5 marks, Objective: To check the productivity of software alongwith its quality comparison with other software and core components of quality. UNITI Introduction Software testing: Testing as an Engincering Activity, Role of Process in Software Quality, Testing as a Process, Software Testing Principles, Tester Role in Software Development, Artifacts of testing (Faults, Errors, and Failures), Limitations of Testing, Challenges in Software Testing, Testing and debugging, Verification, Validation, Test levels, Software Quality: Software Quality, Software Control, Quality Assurance, Quality Assurance Analyst, Quality Factor, Quality Management, Methods of Quality Management, Core components of Quality, Cost Aspect of Quality. (T1(T2}[R3]{No. of hrs. 10] UNITIL White Box and Black Box Testing _ Different Testing Techniques, Differences between testing techniques Black Box Testing: Requirements based testing techniques, Boundary value analysis, Equivalence partitioning, Decision table, State/Graph based testing White Box Testing: Static testing techniques, Static analysis tools, Unit/Code functional testing, Control flow testing, Code complexity testing, Data flow testing Integration, System and Acceptance Testing: Integration testing approaches, System testing, Scenario Testing, Deployment testing, Non-functional testing techniques, Acceptance Testing: Acceptance criteria, types, test cases selection and execution. (TL{T2](R2]{No. of hrs. 10] UNIT II Quality Assurance: Quality Planning, Quality plan objectives, Planning process overview, Business Plan and Quality Plan, TQM (Total Quality Management), TQM concepts, Zero defect movement. ‘Quality Standards: Quality Models/Standards, Standards and guidelines, Types of Models, ISO Standards, CMM and CMMI, Six Sigma concepts, Quality Challenge, National Quality Awards, | (T2I(R1IOR3} [No. of hrs, 10] UNIT iv ‘Test Selection & Minimization for Regression Testing ‘gression testing, Regression test process, Selection of regression tests, Dynamic Slicing, t Minimization, Tools for regression testing. Management and Automation: Test Planning, Management, Execution and Reporting, ftware Test Automation: Scope of automation, Design & Architecture for — sting tools, Object Oriented Testing, [TLJ[R1][R2]{No. of hrs. 10]MODEL TEST PAPER I FIRST TERM EXAMINATION SEVENTH SEMESTER [B.TECH] SOFTWARE TESTING AND QUALITY ASSURANCE [ETCS+03] ‘Timo, 190 Howes ‘MM. :30 Note: QNo.1 is compulsory Attempt any two from the rest. Q.1. (a) Difference betwoon testing and debugging. ® - ‘Testing Debugging 1, Debugging starts from possibly un- Known initial conditions and it's end cannot be predicted, apart from statie- tically 1, Testing always starts with known conditions, uses predefined methods, 2 ‘Testing can and should definitely 2 The procedures for, and period of, ‘be planned, designed, and scheduled. | debugging cannat be so i 3. It proves a programmers failure. & Itis the programmer's vindication. 4, Itis a demonstration of error or 4. It is always treated as a deductive apparent correctness. process. ‘5, Testing as executed should strive & Rebugging demands intuitive leaps, to be predictable, dull, constrained, conjectures, experimentation, and some rigid, and inhuman, freedom also.” 6. Much of the testing can be done & Debugging is impossible without detailed without design knowledge. design knowledge. =” 7. Itean often be done by an outsider Te must be done by an insider, 8 Much of test execution and design | & Automated debugging is still dream for cean be automated. programmers. 9, Testing purpose is to find bug. 9. Debugging purpose is to find cause of bug. Q.1. (b) Explain the role of process in software quality: @ ‘Ans. Software quality management is a management process the goal of which is to develop and manage the quality of software to make sure the product satisfies the user. The goals of SQM (software quality management ) is to make sure a product is in ‘good levels of quality and meets the regulations and standards the customer needs from the product. Software quality managers have to test the product befare it's released to tho market, they do this by a series of steps called the software cycle in order to get the errors in a software and try to fix it befare being released. Their job is not only to make sure the software is in good shape for the consumer, but also to encourage the quality culture to everyone and avoid fraud by protecting their software through proper development. Q.1. (c) Discuss the term “No silver bullets”. @ ‘Ans. ‘No silver bullets” means “there is no single development, in either technalegy or management technique, which by itself promises even one order of magnitude (tenfald) improvement within a decade in productivity, in reliability in simplicity” He alsoEP University-(B:Tech}-Akash Books Example tet case template is as shown, D i ie Aid comer Pre-Conltioos Signin with als authorization Test Steps Sel the cleat module. 2 ner th customer information. a ee Aeron Tae oem ean Peat aris Aes menage Ne 2. eatvys iva ncn the cole toate added ae sand fle. ® Hiecomputer based ection of progres, 3. Explain code complenity testing and data flow testing. a9) Ans, Complexity isa software metric (measurement), used oindcate the complexity ofa program. Itis a quantitative measure of the numberof dependent paths through a program's sourcecode. Cyclomatic complesty i computed using the contro low graph of the program: the ‘nodes ofthe grap correspond to indivisible groups of commands ofa program, and & directed edge connects two nodesif the second command might be exeeuted immediately after the first command. Cyclomatic complesity may also be applied to individual functions, modules, methods or classes within a program.” | (One testing strategy, called basis path testing by McCabe who first proposed it, is totest each linearly independent path through the program: in this cate, the numberof test cases will equal the cyclomatic complexity of the program, = 5. Verification isto check whether the sofware confrms to specifi: tions, ich errors that vericatio enna ‘High Level Brereisegenres Sevnth Semester, Sonar Testing and ‘cut buthas ade ome change te ies ofthe maturity levels and added new pecifieations. pecfy what type of testing and when and how often you s ine the testing tasks and cycles fe and document how to manage testing andthe parameters by which rigorous and tailored to meet the specific needs of meets specified phase level and overall acceptance criteria + Build the information traceability you require to manage testing progress through ‘each software testing fe eyle stage; + Work within traditional, yimodel, Agile, o other preferred software testing cytes ‘Test management most commonly refers tothe atvity of managing the computer d to manage software testing process. A test management ite them (or scheduling their execution). Execution ean be either manual or automat ‘Manual execution: The user will have to perform all the test steps manually and +0 ier acceptance Test ‘Alpha Teng Acceptance Testing - In SDLC: The + Beta Testing ‘eceptance testing in the software development life pee — essme, tre Tig and ony Aarrace cated gait the test data or using an acceptance | est canes are cuted A ing an ace ‘ae cre preva compare withthe pec one ; MODEL TEST PAPER I ne a aoptcrera aes onth aioe falloing Satan ree si anton! Carectnes and Compleenett SEVENTH SEMESTER [B.TECH] . a SOETWARE TESTING AND QUALITY wend ASSURANCE [ETCS-403] ‘Time. Hours i Dees | me n-th tans nce ec ore rae ed ein a ae ay Sa us ef mre complesenaris recat out a ance tat plan athe following atebutets Bor org st [Fasaenee panne Faia on Resor “et evew foo 7 a Jeno tet actives ar designed reach atone ofthe conclusions — = fewer va ara] 1 Acep the stem a ivered roa Aare ams 2 acep the prem afer the rquested modifications have been made aaa = 4. Donut accept the yam Sane vrston abn ‘Acceptance Test Report Attributes Desens ars Decor i ag ‘The Acceptance teet Report has the following ateibute: + Report enter Use can sing + Variations + Recommeadations defects an ero or ab * Summary of T-DO List gn th aplication which sereate. A prog + approval Decision ce mistaken ct ont a et th tee reguremets hen reel into Bg Petadiagram ‘Component tests se erented inthis phase aswell ofthe testing uct and service/process. inorder to tet the pieces of the ty navigning trong ne caves by avigning gh ten eced ous aveoainganae 3g the unchanged parte of check whether previous ‘Tools: Automated Regression Totorboar fn proces stopa when ieas become redone or infrequent. 3 ‘porrded ideas are reviewed for dapiction venjlarifcation, and eliminated whed, necessary. en pn canted wth a Pe pecan Fey cag, onal group tchnigbe oo fand-ffoct diagram. 'Q1. (6) Diseuss various Quality s standards, and many have usabi ch standards ility stand 1 standardizing to an inappropriate eave lees time for quality "tcrarding tothe LEB Comp. Soc. Software standard can be: a ject or measure of comparison that defines or eprosents them aunit Bngineering Standards Commit' "Approach A: excade any unsatisabe obligation from the criterion. "/Zlrmpte: modify statement coverage to require execution ooly of satemeny Ve-METP- Seventh Semester, Software Testing and Quality Aswurance throw new LogicErrox “x must be positive here! LP University (B Tech)-Akash Books Mere sas ‘that can be executed. sot only recording tina complete IDE You can choose tase its Sut we cant know for ure which are exacotabe! "ordng apatite ou may et your uray hand. With ascot upper. TAgpesnh B: measure the extent to which atest mite approaches an adeqy te tered dy Senin IDE th eal earnest eiterion » Features: Lica = Baample: if testsuite satisfies 85 of 100 bligation, we have reached 86 + Bary record and playback — + ltellgent eld selection wil se IDs, names, o XPath as needed “Them An adequacy ritrin is satisfied or not, a coverage measure isthe faction “+ Autocomplete fr al common Selenium commands etified obligations + Walkthrough tert "No tex suite cam satiey statement coverage for this program iit’ correc) * Debug and et breakpoints Meazuring cverage(% of satisfied test obligations) canbe a usefl indicator, 1 Save tats an HTML, Ray script, or any oter forma Ofpropess toward through testsuite, oftblesptsrequiingmareatenin | Super Selenium weeiensiong le ora dangerous seduction ne SE GENGINE -Advetet QEocioe oes integrated soltions to test an verify + Coverage is only a proxy for thoroughness r adequacy foci: ny sod erformance ofboth web applications and web services. Features ‘Test selection approaches Features: Guidance in devising a thorough text suite (QEngine toolbar for remote record/playback ‘Bzample: A specifiation-based criterion may suggest test cases covering 0% web-based tot script creation and maintenance representative combinations of values al-user record playback option eon suoc eas One-click acces to configured suites and test scripts « Post hoe analysis: What might I have missed with this test suite? 2 Single point afar fn performs esting + often in combination SEE eee at temesig 1 ample: Design testsuite rom epecifications, then usestrocturaeitrion(@, | si coverage of al branches) to highlight missed logic _ Berner or unatnded ting ri cary eoimproveeverage without improving atest rite (much ewsertban | 4 nua gts gee nent ne designing good test cases). recone your Sat scipe nay fmtional testing toot includes an HTTP proxy that “The only measure that really matters is (cost) effectiveness. ‘he pig recarer stomatal stores variables posted to fre soa dont hae 3. Explain various tool for regression testing. (25) | wate that stulTby band forms, s0 you doo" have to ‘Ans. ReferQ1. (eof End Term Examination Model Test Pape Pontes {L WATIR -Watiris a simple opensource Library for automating web browser. It open source | 4 Seip are writen in J allonsyou to write tests that are enry to read and easy to maintain. Itis optimized for | > iythoo, an implementation of Python. Python script are sraplcty and exbility. Watir drives browsers te same way people do. I-eleks inks, ) 7 ‘understand, modify and extend, seal Ser and ey Wa re ey eg Tm ota | cles TP my sre ii prem, ee ir SA ra hy in a a a pas ‘Windows. Watir is eurrently being ported to support FireFox and Safar. from the command line so you ean run scripte unattended, ae Pet Tae in a ce cipecenentia “te ee neoourcnng ta eect nt ste ha tara en pn te eet emceero Testing and Quality Assurance they review each other's work, including seu {LP University {B-Tech)-Akash Books MTP enh Semete & Cate a7. Beplaia: (a) Test case template fora company sales interface en fos, D Tie Pre-Conitins ‘eat Stops Expected Results Q7, ©) Quality of good tert case, o ‘Ans. good test case ha certain characteristics which are: 1 Should be accurate and teeta what itis intended to teat, unnecessary steps should be included int shouldbe independent ie You shouldbe able to execute it in any order without pendency on ather tet cases , 7. It should be simple and clear, any tester should be able to understand it by reading once 8. Now keeping in mind these characteristics you can write good and effective test rams aka, Date-driven testing ‘a keyworddriven of table-driven testi ‘Extensively parameterize «+ Reusable steps ereated in a ‘Actual | Comments 5 a ‘Tests only one thing: Always make sure that your tet case tert only one thing, if Step] Fastruction Expect Rovult | Rell ‘you try to test multiple conditions in one test case it becomes very dificult to track ‘osults and errors, ‘or this est, we are Word | Pass 1 | Open up the Mierosot vse MS Word 2003 Organize your test cases consistently: You can organize your tet cases in many i opens. Sa Mt ways however you should always fllow the same pattern o organize ou test cases, Write test cases: Your test cases should nat have dependency on B ‘Anew blank do | Pass other test, ld be able to execute your testcase individually wth having coment is dis ‘Write small test cases: Always mention purpose of each testcase clearly in test Q7. (0) Define Testers. o ved in the quality assurance stage of software ‘The word "bold" is | Pass highlighted ‘The role of a software tester is integral tothe creation of software systems and otis | Pass ‘technical products including vehicles, electronic goods, de ‘Ultimately software testers are employed to find bugs and issues within a product before it gets deployed to everyday users, They can work on bespoke individual projectsth Semester, SftvareTeting and Quality Assurance Seventh Semester, reports have been retalved, to the software, heck which planned deliverables are actually delivered and to ensure that all )T finalize and achive txtware uch a scripts, test environments, tor Ts handover tho tetware tothe maintnane rgtsization. They wil give ton Dnermnt eign tn apation aati taedon besten, inthis we check where the supported les of oftware has been installed o dy tween black box and white box testing Black Box ‘Testing White Box Testing 1. Black box testing is the apftware testing method which is used to test the software without knowing the internal structure of ode or program, ‘White box testing iester, Sofware Testing and Quality Assurance [LP University-(B:Tech}-Akash Books MTP Information Dependency graph: Captures the dataltonto. dependencies among ) Explain non-functional testing approach. 6 Ans. Non Functional Testing that which we tet the application/software against lien’ expectations and performance requirement. In short we an aay this testing Ie {vay validating the performance ofthe application example include Load and Stren , | Testing. graph model that must be covered during esting ‘Step 8: Select test paths to cover those requirements ‘Step 4 Derive test data so that those test paths can be executed Graph Models Control flow graph Captures information about how the control is transferred in a program. Data flow graph: Augments a CFG with data flow,ster, Software Testing and Quality AS eperpst Seventh Sere te MrPat-9 ele managemet ts, management can e 3 ‘Level §- Optimizing: Focusing on continually improving pt through both incremental and innovative technolo eement objectives forthe organization are. Strategy phase. Typically, inthis mine effrt and cost estimates for the project and tified/ereated and is reviewed and thenaware Testing and Quality Assurance LoTR Soe Se eatnvlel) ata (I Tost Enviro LLP. University-{B-Tech}-Akash Books MTP Q2 Explain quality models in softwar 0) ¥y models in software testing. a9) + Understan tecture, environment set-up and prepare hard, and software i PSorup teat Environment and test data + Perform smoke test on the build | Deliverables: iy with tort data setup | this phan test team wil ary out te testing based he ae pansand the ts cases prepared: Bugs wil be reported back to the develo team for correction and rtestng wil be performed. Deliverables + Completed RTM with execution status Tat casos updated with results ‘Tost Cycle Closure: Testing eam will met, discuss and analyze testing: fy strategies that have to be implemented in future, taking lessons frou vities: ‘+ Evaluate cyle completion criteria based on Time,Test coverage, ost, So ‘quantitative reporting of quality ofthe work product te ‘Tat result analysis to Bad out the defect diateibution by type and sven. | Guay af roduc operations doers oe een ee eeety Acs pezni| ri [wera ‘Operaility Training Communic ronan] Rony tame eroneetng Testy [oesearasen| abi ‘AugerMODEL TEST PAPER IT END TERM EXAMINATION SEVENTH SEMESTER [B.TECH] SOFTWARE TESTING AND QUALITY ASSURANCE [ETCS.403] ‘Time. Hours Mas76 is compulsory and ttemptany 4 quedo fram the ret [Aso itis possible tifa clas doesnot contain a bug, it may still be used in a ‘wayby another class, leading to system failure. ist while conducting atest should be stated with each testcase, tates of objec that isto be tested should be specified. in this esting sto détect the rest ttompt to based testing starts by exami bya tohis or ‘an individual user hich the computer's owner(s) oF posed without the consent ofthe ions among various se contol software includes time control functions that empowers parents ose the amount ad to incorrect outputs that can fie tha child ay spend accessing the Internet or laying pares other copter in testing activities describing how a ser mi ‘specific context or environment,MTPAL-t7 and Component tating. * Accoptanen esting of ne uneional enhancement may come bef cencani ing ire asi crt wera fr rod cntom developed sofware Aceptane should be forma ‘when the contract is agreed. tans eld be fms 0 claments required by si led program graph. Bascal1. Preproject components e 2 Pret ie ye ees aneaent tar errr prevention and iPro so-10] 89 | 90 | a | 99 | 100 | 1 plans have been correctly d ea regan poet 1 Contract review 2, Dev Hela] so-so | 79 | a0 | si | as | oo | oo Sek chileCyel Actives Assessment Theproecifecycesompedg | Tpnp | gp | oy | mt | S| 8 | 0 re “ andycogamma| 2) 6 | 6 | a | os | oo | So 1 Tue dovelopment Lifecycle tage:~ Aim to detect dsin and rogra oo} a |o | 1 | | s | a ao} 2 Po} a] ate errors = Its components are divided into: 6. (a) Explain code complexity testing. a complexity metrics measures software attributes maintainability, smization These metris helps in following scenarios code written by some ather person. oftware software in short time period with maximum test coverage and testable. Number of test path direc ty t.can be used directly to allocate testing efforts, in fllowing eub metrics ‘3. Infrastructure error prevention and improvement * The goals of SQA infrastructure are the prevention of software faults, or at the lowering of software faults rates, together with the improvement of product “The components are applied throughout the entire organization + The class of SQA components includes: 1 Procedures and work instruction 2. Template and checklists 8. Staff training, retraining, and certiation 4. Preventive and corrective actions shouldbe followed fr computing Cyclomatic complexity and izm. struction of graph with nodes and edges from the code lity Assurance has always been an evolving challenge in so development. Are we doing enough? Are we catching the right bugs? These areal that cross cur minds during the process. Each of us has a different way of dealing «addressing these questions and more. A project team these days may include mult developers, project managers, designers, solutions architects, supervisors and.ware Teting and Quality Assurance Semester, Sot snaepst Seventh Beano sia be gap 2 camber of noes present ot oe nent ly ens report spt 3 arenes they old age on a eel reper, Ba awn sn aly he ta ls not uncommon to hare a tats meeting everyday (or meet preeat QA team's status to the concerned parties. Bi “ ee the mode ofa status report can be: i. communication sent ou to establish transparency the day daring the test cycle ~ includes both defect SE semen minectng : Ge iinet een TE emu wna) | neg wot eeemensmmeceeemereceamasa ad | Sti faa uaauarnmuapmenitense ee meee camel iShares er a Pace Smear ST ge esa a business, whether or ‘Test plan status ‘ot the Business needs nev loans or new investments. Businesses need plans to optics Test documentation status {growth and development according to priorities, ‘Test execution statusdefect status) ‘A simple start-up plan includes a summary, mission statement, keys to success, 5 Ssgjwn Market analysis, and break-even analysis. This Kind of plan's good for deciding whether Fr Fees cneuth to communicate with the reat of the project. teamis,"M Gr not to proceed with a plan, to ell if there is a Business worth pursing Dati * i ‘enough to run a business with, tai : ‘Annormal business plan (one that follows the advice of business expert) includes a fathering and other activities have begun and also when the are finished. THA %4 standard ae of slements, Business plan layouts and oulsnes any buted ete 3¢ teas will include components such as descriptions ofthe company, prodict or service, marta, forecasts, management team, and financial nalysia.ackgrounds of ey members fhe ta toa ensh flow, balance sheet, break ew and nae be : 1 eprint CODA OT Iason dally pans maybe Shute eerie ra brreeiens planning addresses develc Qmagenet em, programme * Quality management sytem scope: Who an what FIRST TERM EXAMINATION [SEPT. 2016] SEVENTH SEMESTER [B.TECH] SOFTWARE TESTING AND QUALITY ASSURANCE [ETCS-403] mpl: process so quality management system. Verification seope + Organisation & responsi + Cost benefit analysis: A quality program cost benefit analysis addressing’ such asthe cost of poor quality the east a Smprove quality and the cost benefits 1 Verifcatin isa state practice of veriffing documents, design, code ci the software conforms to specifi: tions 1s « dyoumic mechanism of and toting the actual prodct. 2. Italways involves executing the cod, 8 tiscomputer based execution of program.‘Seventh Semester, Software Teting and Qt anchor tal ve Tov ‘various conditions and their cotrespo is divided into four pars, on be taken for certain posible condition ae listed by action state ions tobe undertaken when selected condi Decision Rule 2 [Decision Rules 0 100 2 N Set State to “fall con 2) What do youean by software quality, quality asrurance and Requires very sled tester hale thi elation pstvel and even by competi sway There are simply hundreds af excuses developers tens ak ‘unt For this tester eo reuier ood ings the renin ting wok ipl beeen current fncoality change, revues eks and bug tracking. o ls ardeven Sonn, Star Toning nd ANY 6 von mean by Boundary Value Anal aed on toting at the boundarig ae ions) and oundaries (in the ¥ ‘The goal of wat testi individ parts are correct ing isto isolate each part of the program and she {h terms of requirements and funetionality T ‘The determination ofthe functionality thatthe intended application evaluate every execation path in every software appl fanittesting is moant to perform, ‘Theres limit tothe numberof scenarios ‘The creation of test data to verify a source code After having éxhausted all the options, there is no cho ‘The output based on t application ‘op unit testing and merge the code segment with other units Integration Testing Integration testing is defined as the testing of combined parts of an app dcermine if they function correctly Integration testing can be done in two ways: “upintogration testing and Top-down integration testing. ‘Bottom-up integration : This testing begins with unit testing, followed! progressively higher-level combinations of units called modules or ‘The writing of test scenarios and the execution of test cate, ‘The comparison of actual and expected results based on the executed Examples: Performance Testing, Load Testing, Stress Testingsting and Quay Asturance sameser, Sore Sern er reuned when te sobeodele# a6 r6007 Bilt LP. Univectity-[B-Tech}-Akash Books 2016-9 sways distinguish as “called programy test the interface between them to check rap down approach), it used whe esting activity that wes scenarios: hypothetical my modules which are y ‘complex problem or tot system, The ideal bottom up integration measure of iy means & weiplined, datacdriven ap system events and how does the aystem handle such requests ts and create end-to-end taths to check them. ‘competitors preducts and their predecessor mnWhat are different types 1d yet powerful : the difference between system testing and accep ‘Ans Acceptance testing a pare functional testing to check ce system bl ‘Acceptance Moderator Person responsible toensure the discussions proceed on the productive lines. al interfaces. The system testing comes undef! Reader: Person responsible for reading aloud small logical units ofthe work ign or structure or code ig can be of functional Recorder: Person who records/documents all the defects that arise from the spector:All ofthe inspection team members who analyze and detect the defects6, Debugging is impossible without detailed) design knowledge 7. Itean often be done by an outsider. 8, Automated debugging is stil a dream for programmers, 9. Debugzing purpose isto find cause of big Software validation i an important ol employed to asure the quality sroducts. Few benefits are as under: : on eau of uman © output beng rset pa alu bingenteredor on OOD eee fares may also be caused by someone di am Q: he to stop testing is a crucial decision. What factors conics or aking sucha decison: seranicon facto haere taken nto aepunt when deciding stp testing ar * {Deadly lease deadlines, testing dealines eeiamcaeeas | ranged and annual quality targets. Oe enacting go bararssend heaanenctier] "SEA cesta ators you, x and reliability of the device software, reruling in recalls and corrective acto be in charge of quality ascurance, organizes Quality Review Meetings, and establishes ‘Amount of code, functionality, or requirements to be covered and manages organizations to prome ity assurance ‘Minimum accepted bug rate; 8. Quality Assurance Edveaton: This fneton eda l emplyet sot ‘quality and improves employees’ problem solving’ training targeting tion ofbeta or alpha testing periods. : wally en Q3. (a) What is the difference between. and debugging a Ans: Debugging is conducted by a programmer and the programmers fxtb®@ commen: es an als onganies,doemnate, maataine, and improves the business daring deoging phase Tester never te erors, but rather fined them 808° ‘eandardssaiaie fr cach busines or the product character, oe ;216-19 toimerove tn gut its warren errors AUAKIME Tyglity Assurance = ese Star Ten b [LP University {B.Teeh}-Akash Books 2016-15, es may be < Expected Outpat 25 Not Quadratic. 25 Real Root 25 Imaginary Rots 2 Traginary Rots 25 Imaginary Rots 25 Imaginary Rots 33 Imaginary Roots 25 Imaginary Rots 35 Equal Rvts ° Real Roots 1 Real Roots “ Imaginary Roots a0 Imaginary Roots ting. How are surveys helpful in post Step 4: Calculation of Cyelomatic Complexity V(G) by three methods ‘Method: Vi 229-186 225 42=7 | mare predicate nodes with 2 outgoing sAvegions + 1=.6 +157 Survey questions were designed tore [RS & R6 are the enclosed regions and 1 corresponds tofuportant within is same by all the three methods. | 1 program to determine nature of roots of a a1 lore performance tag Not aguadatc guatin Real ots, Imaginary rootuequalroot DO rept tn dent agreed that designing post d 7 percent of respondent st “esgning post deployment robust et cans forthe giver program formance esting" aerial task, Satatven percent epee that peroraasre ‘Ans. Consider program forthe determination the nature of roots of aqui : j eee how companies are defining what's most This provides a glimpse intoa, estat aaa “Shanges in the sof starting and nl Ma SoM rc Seinen taetonteemace ne nme pares i ae oftware enn idea behind Six Sigma: If you can meas ru can systematically figure out how to "er as possible and specifically it means a fa ion or 99:9997% perfect. ‘concepts of Six Sigma: ritical to Quality: Attributes most important tothe customer. ) ina set of activities for ensuring aus Sa iy revult in quality in sofware pi processes to improve pabilty. oun ananent une Derdowen Magen! st an ae ty criteria is an attribute se ecient sf wloare (e) Batmation or example, modular (0 Soteare Design dent eres, mt pbc sad ‘List of McCall's Quality Criteria: ve ith which the software and data can be checked for nee the processes have been defined and implemented, Quality Assurans Access Audit ‘atuwingresponsilies dently weaknesses in the proesses correc those wet!” compliance with sta tocontinually improve the process 2 Access Control : Provisions for control and protection ofthe softwareExcellent 12 | Oracle, MySQL, MS SQL, PostgreSQL, DB2, ronment | Firebird "Annual Increment depends on the earned points. Generate test cases equivalence class testing and decision table based testing. at "hms The cases generated on the basis of equivalence class Testing ar""*"S1°" Sexs0 Excellent sas0 Very Good 19 sect Good G9exe5 Average x<5 PoorNaxos [Maly foued er. | ur data What ie dynamin ram testing te process of ent ‘Anas Tost data generation in POC Tea, One of the documents and provides review comments ‘Work document ean be of following: Retest Regression Test ‘Seecton Prontzaton ot “Test Canoe (a) Retest All ‘This is one of the methods for regression testing in which all the tests in the {sisting teat bucket or suite should bere-executed. This is very expensive as it requires ‘huge time and resources. emoFIRST TERM EXAMINATION [SEPT. 2017] SEVENTH SEMESTER [B.TECH] SOFTWARE TESTING AND QUALITY ASSURANCE [ETCS-403] me: 1% hee, MM. 30 ‘te: @.No.tincomplsory. Attempt any 2 questions from the rest @ !approach in which al possible data combinations tng includes implicit data combinations presenti of testing @ This typeof testing is performed by developers before the setup is handed over esting teum to formally execute the tet canes, Unit testing a orioraned oF the rs on the individual units of source code aasigned areas, The ‘suite, The test suite often also contains more collection of test eases. It definitely contains & system configuration used during testing. Agroup [et eases may also contain prerequisite states or steps, and deseriptinns sr, wing teats QA. @) Limitations of Testing. @ ‘Ana. Testing Limitations + You cannot tes a program completely + Wecan only test against system requirements=e sot uty Aare arse LP Unie {0h Aaa oa ann So ana i | at et cn a te os ay nt ete ge no Maw enePin and eror handing eae ta fw irmation T fhcomplee or ambient ine in present acer pe oding practices the seta isonet Py eae planing te | White Box Testing Approach ofan exany, To write Test Cases for White Box Testing, "4 The tester analyzes and understands the sree Bx isthe structure ofthe system by examining g., Th tester understands the weak spots within the eae that is most prone to a whi ‘Test Qa.te) or Tube internal working ofthe system whi ing ‘Ane When the ester as 03 eating In thease, the nyse unde he statements within the code must have testcase ack bon ning prmene iets statement must be executed a least ence during the Taaiements Document or Ronen and ihe procenste within the tn = ts: Al the decision directions mart be executed at lear once during yithin the system are S tps toinctadensome negtive at cases with svali NPS ANd execution, tested by paning the speci variables through ack pate tyes eeepc orminaton) aa sppable + Multiple Condition este: Ti wil ensure that each pit of try within the Tehqcs of lack Bor Teting ‘ela tnted at east once drig tne tengo ple Tapa nae the highest probability of ving erroneous OUtpULS. grrlated toa numberof coding eros Tew alclated by developing a Cones] Flow a racivalence Class Partitioning: In thie approach, a limited set of fucsraph ofthe code that measures the numberof near sndependent pathe through a inidentfe along with te corresponding vali and invalid inputs and expectedu module Fetes ohio atidentiping cases of errors and therefore reducing the a Lawer the Program's cyclomatic complexity, lower the risk to modify and easier t» test cases eure nderstand. Tecan be represented using the below formula ‘Error Guessing: An experienced tester most often usee this approash's|_ Cyclomatic complesity = EN + 2°P ‘Ment the defect and then develop corresponding tet cases, where, ‘White os Testing In white box tating methodology the tester has the oss! E'= numberof edges in the flow graph ofthe internal of system and knows how the system is implemented. The tes. N= number of nodes inthe flow grap,rae Expected Output] ty Assurance : e senna sig a LP Univerniy-8 Tech Akash Books aor sent seve! ibe used to calculate MTBF, that is, MTBP = MTIF +MTIR vo ne path llowed a peri = Maint Insofiware engineering software maintenance is oneof tho most i suming activities. Maintainabiity can be defined as the ease ‘ ith we product can be modified to correct errors, to mect new i make future maintenance easier, or adept tothe changed envionment. that software maintainability is assessed by using indirect measures like Mean. to Change (MTTO), which can be defined as the ime taken to analyze change est, design modifications, implement changes, testing, and distribute changes to guarantee 100% branch cowl ysers, Generally it has ben observed that programs having lower MITC are easier werage but it does | ‘program, Input for tet cases are given asTamer can spat the apliaton ra. The CO ate an eh B&O secant nen le pe ctbar an, Drier ey oie te tiation ples ae the tbe OF code are te hs bottom up eating APPronch, a otras ott mn istinguinh a “alle proera ne hat ae em paens ted only used when ai (3) Establish ‘Ane uing canbe eine at -Aprocns of analaing a ofa ton ne ing od required conditions (ati fectaerrort Se ied pun Veriton ake place fiat and inl eaten sod ‘ecing for dcumentat {avoles the checking Q.1. () What are various kinds of functional testing? Briefly deserit ibe ites namagec tng cng tt dont ta tion, coe, ele Validation cars ater verif the overall product. functionality ofthe eytem or Software, sould cover all the scenarios paths and byundary caves. The other major Functional Testing techniques ines {reas The developers ute test data that is diferent from the test data of the Sevorance eam, z aon Tee tn agen ts a} fan plains detrei the anton, correty Integration testing e ntwo ways: Bottom-up in up integration testing and Top-down integration testi: | Na -“effort. + Compromise between thoroughness and budget. to make business decisions for release dates, ast bug, oul never know it ‘before you run out of test cases2A activites eneure that the process is defined and appropriate. Methodsloy ‘andarde development are examples of QA activities. A@A review would feces L_100 and marks > 100| mark is invai ark? > 100 and 0 mark 100) (sarki invalid mark fand mark2<0 and 0 mark < 100) (markt is invalid, mark jand mark3 is valid) ‘and mark2 <0 and marks > 100 (markt i valid, mark is ia)sLss Sens 8 ‘Table 2: Test eases ofthe given problem ‘markt marks a 101 50 50. | 50 | 50 2 5 2 1 A . is eyLP. Univers (OB Men, tn oma caneg te Pe Je where mult mac ce a vere " vt oe nn combinations sheet follwing equivalence clasee, “The input domain may be partitioned into th 'A1 0 mark1 $100) lions given below: () Fail Gi) Third division (ii) Second division (iv) First division () First ‘with distinction (vi) Invalid marks. wT Paplaia the steps of Data Flow Tsing. Draw low raph for eben os and dl devpatia and identity thove dupath that are fineness Ae nitions and generatetat caves for these a3) 1 tmtfunctlonZiinty) 12 euelt(es 7=00 st 13, @&y=D) ——20-2017 soventh Semester, Sofare Testing and Quality Assurance wy ton at iJ ° fren =00 88 nd lee aa eee int tite”, =) 20° pris Ls 21 return 0; Treat onesie Renan cama ; fotmarth aaah 06 ao et ner marks 3 mbt Cntr 010087; cancer te et he ; miners ant, wart pac rk én sabe, cacnd emer, Tanner ced uct 1 else iffavg>d08&eaygc50) | printf("Phird Diviston*r ’ ls iffavg>=508 Rave’<60) | rintfSecond Division"), ’ 7 lee iffavg>=608-avgc78) | rintRFirst vision’; , ropam tooutputdvsionarawtugentDared on tD© TAKS in threy LP. Uni \ Meri Teh a, th Books printf(“Pirat Divi define/ use nodes fr all variables ae given blow Variable Defined at node markt 7 smark2 9 (marks un we, 18Ss “joy dapat, al ore8 “Al dovpath and all-use ‘All definitions 617 Yeo “Tet cases for all du-pathe and al-uss are given in Table 1 and testa efinitions are given in Table. ‘Table 1. Test eases for all du-paths and all-uses ‘SNe. Romaary Toad ok bin he edocuments in SQA? so essential to TQM that many organization define ‘core values and principles on which the orpuniaton is key principles: to requirements, not some sort of time than to corret problems tas the quali reeization, Business performan ™ iof Test prioritize the test cance depending on business impact, rica & frequent Me Selection of test cases based on priority wil erally reduce theRR “AlN natn of hc taint be ttd should bo specified.‘resting and Quality Assurane, test canes y big Regression oat whan GUL struck Reusing the regression gq) regression ceording to new GUI. But thig yyy tet eo S cumbersome if you testing tools are; + Regression Tester + V Test + Watir + Seldhium + actiWate + Rational Functional Tester z Slicing (e) Dynamic : ( sean The conventional notion of program alice the set of al statements ta, ‘affect the value of a variable occurrence is totally independent of the 5 values. Program debugging, however, involves analyzing the program behavicr , the specific inputs that revealed the bug. Dynamic Slicing (DS) identifies the , ‘executed instructions (called dynamic slice) that had directly or transitively contri, to the value of the variable, DS is achieved by tracking program dependences on ti, ‘The challenges o£DS lie in the cost and the large size of the produced slices, Dynamic information flow tracking (DIFT) tracks if confidential informatica, ‘as user password is leaked during program execution, or if untrusted informatica| external sources contaminates critical part of program execution. Technically | shares a lot of similarity with DS as it also relies on tracking program depend ‘and hence faces similar challenges,