Question Set I (Basics of Software Testing and Life cycle Testing)

1. To test a function, the programmer has to write a tested and passes it test data. a. Stu! !. "ri#er c. $ro%y d. &one of the a!o#e $ic( the !est definition of )uality a. Quality is *o! one !. +ero defects c. ,onformance to re)uirements d. -or( as designed , which calls the function to !e

'.

..

"uring the software de#elopment process, at what point can the test process start/ a. -hen the code is complete. !. -hen the design is complete. c. -hen the software re)uirements ha#e !een appro#ed. d. -hen the first code module is ready for unit testing 1cceptance test cases are !ased on what/ a. 2e)uirements !. "esign c. ,ode d. "ecision ta!le -hich of the following is &4T part of system testing/ a) !usiness process5!ased testing !) performance, load and stress testing c) usa!ility testing d) top5down integration testing

3.

6.

-hich of the following is &4T a reasona!le test o!*ecti#e7 a) to find faults in the software !) to pro#e that the software has no faults c) to gi#e confidence in the software d) to find performance pro!lems -hich of the following are #alid o!*ecti#es for testing/ i. To find defects. ii. To gain confidence in the le#el of )uality. iii. To identify the cause of defects. i#. To pre#ent defects. 1 i, ii, and iii. B ii, iii and i#. , i, ii and i#. " i,iii and i#.

8.

9. The cost of fi%ing a fault7 a) is not important !) increases the later as fault is found c) decreases the later as fault is found d) can ne#er !e determined :. ;ista(e < error are similar.. similarly what word is similar to this.. a) defect < error !) defect < !ug c) !ug < error d) failure < error 1=. "escri!e what the following terms mean7 >rror7 ?ault7 ?ailure7

11. >%hausti#e Testing is a) Is impractical !ut possi!le !) Is practically possi!le c) Is impractical and impossi!le d) Is always possi!le 1'. -hich of the following should &4T normally !e an o!*ecti#e for a test/ a) To find faults in the software. !) To assess whether the software is ready for release. c) To demonstrate that the software doesn@t wor(. d) To pro#e that the software is correct. 1.. 1 failure is7 a) found in the softwareA the result of an error. !) departure from specified !eha#iour. c) an incorrect step, process or data definition in a computer program. d) a human action that produces an incorrect result. 10. -hat is the o!*ecti#e of de!ugging/ i To localise a defect. ii To fi% a defect. iii To show #alue. i# To increase the range of testing. 1 i, iii. B ii, iii, i#. , ii, i#. " i, ii. 13 ,ontinuous ,hange which model a) B5;odel !) 1gile 16 . -hat is the important criterion in deciding what testing techni)ue to use/ a.) how well you (now a particular techni)ue !.) the o!*ecti#e of the test c.) how appropriate the techni)ue is for testing the application d.) whether there is a tool to support the techni)ue

18.

19.

-hy test cases means no defect a) e%hausti#e testing is impossi!le !) human done testing so chances of mista(e due to software !eha#ior c) due to software !eha#iour -hich one of the following statements a!out system testing is &4T true/ a) System tests are often performed !y independent teams. !) ?unctional testing is used more than structural testing. c) ?aults found during system tests can !e #ery e%pensi#e to fi%. d) >nd5users should !e in#ol#ed in system tests

1:. -hich of the following is true of the B5model/ a) It states that modules are tested against user re)uirements. !) It only models the testing phase. c) It specifies the test techni)ues to !e used. d) It includes the #erification of designs. '=. The oracle assumption7 a) is that there is some e%isting system against which test output may !e chec(ed. !) is that the tester can routinely identify the correct outcome of a test. c) is that the tester (nows e#erything a!out the software under test. d) is that the tests are re#iewed !y e%perienced testers. '1. -hich of the following is a form of functional testing/ a) Boundary #alue analysis !) Csa!ility testing c) $erformance testing d) Security testing

''. -hich one of the following descri!es the ma*or !enefit of #erification early in the life cycle/ a) It allows the identification of changes in user re)uirements. !) It facilitates timely set up of the test en#ironment. c) It reduces defect multiplication. d) It allows testers to !ecome in#ol#ed early in the pro*ect '.. Integration testing in the small7 a) tests the indi#idual components that ha#e !een de#eloped. !) tests interactions !etween modules or su!systems. c) only uses components that form part of the li#e system. d) tests interfaces to other systems. '0. -hen what is #isi!le to end5users is a de#iation from the specific or e%pected !eha#ior, this is called7 a) an error !) a fault c) a failure d) a defect e) a mista(e '3. -hich of the following is not part of $erformance Testing7 a) ;easuring response time !) ;easuring transaction rates c) 2eco#ery testing d) Simulating many users e) Denerating many transactions '6. Software testing acti#ities should start a) as soon as the code is written !) during the design stage c) when the re)uirements ha#e !een formally documented d) as soon as possi!le in the de#elopment life cycle

'8. ?aults found !y users are due to7 a) $oor )uality software !) $oor software and poor testing c) !ad luc( d) insufficient time for testing '9. -hat is the main reason for testing software !efore releasing it/ a) to show that system will wor( after release !) to decide when the software is of sufficient )uality to release c) to find as many !ugs as possi!le !efore release d) to gi#e information for a ris( !ased decision a!out release ':. -hich of the following statements is not true a) $erformance testing can !e done during unit testing as well as during the testing of whole system !) The acceptance test does not necessarily include a regression test c) Berification acti#ities should not in#ol#e testers (re#iews, inspections etc) d) Test en#ironments should !e as similar to production en#ironments as possi!le .=. -hen reporting faults found to de#elopers, testers should !e7 a) as polite, constructi#e and helpful as possi!le !) firm a!out insisting that a !ug is not a EfeatureF if it should !e fi%ed c) diplomatic, sensiti#e to the way they may react to criticism d) 1ll of the a!o#e .1. -hich of the following is the !est source of >%pected 4utcomes for Cser 1cceptance Test scripts/ a) 1ctual results !) $rogram specification c) Cser re)uirements d) System specification .'. >nough testing has !een performed when7 a) !) c) d) time runs out. the re)uired le#el of confidence has !een achie#ed. no more faults are found. the users won@t find any serious faults

.. -hich of the following re)uirements is testa!le/ a) The system shall !e user friendly. !) The safety5critical parts of the system shall contain = faults. c) The response time shall !e less than one second for the specified design load. d) The system shall !e !uilt to !e porta!le. .0 In prioritising what to test, the most important o!*ecti#e is to7 a) find as many faults as possi!le. !) test high ris( areas. c) o!tain good test co#erage. d) test whate#er is easiest to test. .3 . -hich of the following is true of the B5model/ a) It states that modules are tested against user re)uirements. !) It only models the testing phase. c) It specifies the test techni)ues to !e used. d) It includes the #erification of designs. .6. Gow would you estimate the amount of re5testing li(ely to !e re)uired/
a) Metrics from previous similar projects b) Discussions with the development team c) Time allocated for regression testing d) a & b

.8

1lpha testing is7 a) post5release testing !y end user representati#es at the de#eloper@s site. !) the first testing that is performed. c) pre5release testing !y end user representati#es at the de#eloper@s site. d) pre5release testing !y end user representati#es at their sites.

.9. 1 failure is7 a) found in the softwareA the result of an error. !) departure from specified !eha#iour. c) an incorrect step, process or data definition in a computer program. d) a human action that produces an incorrect result.
39

1 de#iation from the specified or e%pected !eha#iour that is #isi!le to end5users is called7 a) an error !) a fault c) a failure d) a defect

0=. 2egression testing should !e performed7

v) w) x) y) ) a) b) c) d) every week after the software has changed as often as possible when the environment has changed when the project manager says

v & w are true! x! y & are false w! x & y are true! v & are false w & y are true! v! x & are false w is true! v! x! y & are false