SOFTWARE ENGINEERING

1 Why does software have bugs 1. 2. 3. #. $ns% 2 3 The correct order of the different hases of testing is& 1. 2. 3. #. $ns% 3 2 We get the information about which feature needs to be tested and which feature need not be tested from ((((( 1. 2. 3. #. $ns% # 2 What is a Wa!-through. 1. 2. 3. #. $ns% / 2 0unctiona! Testing is a!so ca!!ed as ((((((( 1. 2. 3. #. $ns% 3 1 What is the need for Test +!anning. 1. 2. 3. #. $ns% # Test !anning needs to be done so that we can com !ete the ro4ect in time Test !anning needs to be done so that we can understand the re*uirement Test !anning needs to be done so that we can understand and met the re*uirement Test !anning needs to be done as it defines the re*uirements of the of the ro4ect that needs to be tested and the sco e of testing can be defined 1!ac- 1o" Testing Stress Testing 'sabi!ity Testing 2oad Testing Wa!-ing through the code Informa! meeting for eva!uation of the documents Navigate through the entire system None of the above System )e*uirement S ecification Test +!an 'nit Test !an 'ser )e*uirement ,ocument System, Integration, 'nit, 'ser $cce tance 'nit, Integration, System, 'ser $cce tance Integration, 'nit System, 'ser $cce tance System,'nit, Integration, , 'ser $cce tance It is good to have software with bugs Not Sure Miscommunication, Time ressures, Software com !e"ity $!! of the above

#. 1. 1. )e6testing after fi"es $nother name for b!ac.1o" Testing. Testing a rogram from the e"terna! view Testing based on -now!edge of the interna! !ogic )e6testing after fi"es $!! of the above $ns% 7 2 What is )egression Testing. 3. 3. 3. Testing done by the deve!o ment team Testing done by end users to verify that the system functions as intended against the re*uirement Testing done by the ro4ect team to to verify the wor-ing of the system Testing done after acce ting the de!ivery of the roduct $ns% 11 2 When do we create the test !ans. Test Test Test Test !ans are created 4ust after the roduct is de!ivered !ans are created 4ust after the testing effort is com !eted !ans are created before coding !an is created after 'nit Testing $ns% 12 3 What is 1!ac. 3. #. More forma!i. It is rocess of using the software a !ication as er the s ecification in the intended use of environment It is the rocess of creating a Testing software for an intended use $ns% 19 2 What is $cce tance Testing. 1. 2. 2. 1.bo" testing $nother name for white bo" testing $nother name for 2oad Testing $ns% 8 1 What is Software Testing. #. Testing a rogram from the e"terna! view Testing based on -now!edge of the interna! !ogic Testing done by the user None of the above $ns% 13 1 What:s an Ins ection. 3. #. 1. 1. 1.5 What is White 1o" Testing. #. 2.ed than a :Wa!-through: Ins ecting the software $!! of the above None of the above $ns% 1 . 2. 3. 2. 3. 2. #. It is the rocess of deve!o ing the software a !ication It is the rocess of e"ecuting a software system to determine whether it matches its s ecification and e"ecutes in its intended environment. 2. #.

#.eve!o er Tester <nd 'ser=>!ient +ro4ect Manager $ns% 17 3 Integration testing verifies & 1. 3. 3. Testing done by a grou of eo !e Testing done for a sing!e com onent Testing done for the entire system as a who!e $ns% 15 1 The acce tance Testing is done by the (((((((((( 1. 1. 2. #. . 3. #. #. Integration testing verifies whether the interfaces between different com onents or modu!es are correct. 1. #. !oo s etc. Testing done by a grou for a sma!! iece of code Testing done on a co!!ection of com onents that constitutes a de!iverab!e roduct. 2. #. 1. the entire domain must be considered to satisfy the criteria Testing done for a sing!e com onent $!! of the above $ns% 2 . 2. Testing that has the focus is on the subset of the domain that re resents communication between the com onents. Integration testing verifies the unit or a rogram against corres onding detai!ed design to ensure com !eteness.1# What is 'nit Testing. 2. 3. 'sua!!y. 1. 3. Tests done for a co!!ection of software com onents Tests done for individua! software com onents Tests done for a!! the com onents of the entire software $!! of the above $ns% 1/ 2 What is 2oad Testing. 2. Testing of many a !ications Testing an a !ication with no !oad Testing an a !ication under heavy !oads None of the above $ns% 13 3 What is Integration Testing. 3. in addition to chec-ing boundary cases. Integration Testing verifies a sing!e com onent $!! of the above $ns% 18 2 What is System Testing. 2.

0i"ed. 2.ebugging is a rocess which can be ((((((((( 1.esign to ensure com !eteness. $ story about the system $ *uestion which we as. 0i"ed. #. 3. $ssigned. Tested ? en. 2. $ssigned. >!osed >!osed. 3. We are verifying the unit or a rogram against corres onding detai!ed design to ensure com !eteness. We are verifying the the entire system against re*uirement corres onding . #. Testing the res onse time of the system Trac-ing the defects or bug Testing the functiona!ity of the system $!! of the above $ns% 22 3 Testing the rocess of ((((((((( 1. designed and schedu!ed $!! of the above $ns% 2/ 3 $ Test >ase is a (((((((((( 1.to the rogram $n artifact which gives information about the user re*uirements $n artifact which gives information about the detai!ed design of the system $ns% 23 2 In a 1ug 2ife >yc!e rocess. #. 3. 2. in addition to chec-ing boundary cases.esigned. ? en. Tested. 2. Tested . !anned and schedu!ed None of the above $ns% 2# # Testing is a rocess which can be ((((((((( 1. Which can be done without any -now!edge of the system $utomated . >!osed Tested.etai!ed . 3. #. $ssign. ?riented to :detection: $!! of the above $ns% 23 # . Tested. #. what is that we are verifying 1. 3. #. $ssign. 2. 1. 2. ? en. ? en. Identifying defects >ertifying a roduct to be bug free and verifying its com !iance with 'ser )e*uirements. The end users are verifying the the entire system against re*uirement None of the above $ns% 21 1 Win)unner is a too! which is used for ((((((( 1. Which cannot be @+redicted@ >annot be automated +!anned. 0i"ed. which of the fo!!owing is the order of the status of bugs. !oo s etc. #. 2.uring unit testing. 0i"ed. 3.29 . 3.

#. The number of defects Ste s to re roduce the bug The critica!ity of the bugs $!! of the above $ns% 27 # (((((((( is a defect trac-ing too! 1. 3.irector Win)unner 2oad)unner None of the above $ns% 28 2 ((((((((( is a 2oad Testing too! 1. 2. To identify.e erformance bott!enec-s $ssess the erformance of the software <nsure that the a !ication wi!! erform as re*uired once de !oyed $!! of the above . 2. To !oad the system under test To chec. 3. #. #. The efficiency and the schedu!e variance of the testing effort It is the information about the testing To -now the efficiency of the code written $!! of the above $ns% 31 1 Segue Si!. #.Test is a ((((((((((( 1. #. #.+erfromer Mercury Interactive 2oad)unner >om are A$ 2oad $!! of the above $ns% 39 # Metrics for the testing effort is co!!ated to -now (((((((((( 1. Segue Si!. 2. Test . 2.efect trac-ing too! $utomated testing too! $ too!s used to generate the test cases None of the above $ns% 32 2 +erformance Testing is done to (((((((((( 1. 3. #. iso!ate. 3. 2.$ns% 25 3 The im ortant information that needs to be rovided in the 1ug trac-ing and re orting is 1. 2. 3.the functiona! erformance of the system under test What oint the system:s res onse time degrades or fai!s $!! of the above $ns% 33 3 +erformance Testing is done to ((((((((( 1. 3. 3. 2. . and ana!y.

2. 3. #. #. The rocess of determining whether or not the roduct of given hase fu!fi!!s s ecification from the revious hase The rocess is to verify the software The rocess which is not re!ated to software None of the above $ns% 1 . 2. 2. 2. 3. The bottom !eve! modu!es are @stubbed@ The to !eve! modu!es are @stubbed@ The midd!e !eve! modu!es are @stubbed@ None of the above $ns% 37 1 1ottom6u testing is a rocess in which ((((((( 1. 2. #. The !owest !eve! modu!es are stubbed The !owest !eve! modu!es are tested first with the use of a driver to simu!ate the to !eve! modu!es Testing done a sma!! iece of code $!! of the above $ns% 38 2 What is Cerification. 2ow Bigh Medium $!! of the above $ns% 3/ 2 There is inconsistency in the data which is being dis !ayed and it does not im act system . 1. 3. This ty e defect can be c!assified into (((((((( 1. 3.$ns% 3# # There is a system crash. 3. This ty e defect can be c!assified into (((((((( 1. This ty e defect can be c!assified into ((((((( 1. #. 2ow Bigh Medium $!! of the above $ns% 33 3 There is formatting error is the error message dis !ay. #. #. 2ow Bigh Medium $!! of the above $ns% 35 1 To 6down testing is a rocess in which (((((((( 1. 3. 2.

3. it is fi"ed correct!y and the fi" didn:t brea. F0inding fau!t with the +roductG F>orrecting the +roductG 1oth D$% and D1% None of the above $ns% #/ 3 $s a tester what do you do when you find a 1ug.#9 What is Ca!idation. $!ert the deve!o ers that a bug e"ists Show the deve!o ers how to re roduce the bug <nsure that if the deve!o ers fi" the bug. #. 3. 0ind cases where the rogram does not do what it is su osed to do 0ind cases where the rogram does things it is not su osed to do.esignG and F>odingG. F. #. 2. #. 2. The rocess is to chec. Ees No Not Sure None of the above $ns% #3 2 Testing accom !ishes the fo!!owing goa!s& 1. #. 2. 3. #. 3. 2. 1. 1oth D$% and D1% None of the above $ns% ## 3 FIf +roducing the +roduct G is e*uiva!ent to F)e*uirementsG. 2. #. then Testing is e*uiva!ent to& 1. <"ecute a rogram with the intention of roving the correctness of the rogram.anything e!se $!! of the above $ns% # . To identify discre ancies between actua! resu!ts and correct or e" ected behavior 1oth D$% and D1% None of the above $ns% #2 3 Testing can revent errors from occurring 1. 3. 3. 1.the software The rocess of eva!uating the software at the end of deve!o ment to ensure com !iance with the re*uirements The rocess which is not re!ated to software None of the above $ns% #1 2 Testing is a rocess to ((((((( 1. 2.

res onse time. 1. 2. 1.onHt want to fai! $!! the above $ns% #7 # What is ro!e of a Tester. Measure severa! system characteristics. 1e!ief that the system wor-s Negative attitude towards effective testing . through ut. Which wi!! not a!!ow the system to wor. 3. #.#3 +erformance testing is done to (((((((((( 1. 3. Tester has to !og his observations during Testing Tester has to !og the bugs he found during testing and fi" them Tester has to review the code and de!iver the corrected version None of the above $ns% #8 1 Semantic error means (((((( 1. #. where as deve!o er is not so #None of the above 1 /2 Testing activities can automated if @(((((((@ 1The test se*uence of actions can be defined 2The test se*uence of actions is re eated 30or erforming the )egression.eve!o er:s aim is to rove the roduct.@ Measure the number of defects the system wi!! roduce Measure the system time None of the above $ns% #5 1 What are myths of Testing . and efficiency. 3.further Which roduce wrong out ut System wi!! roduce right resu!ts but re*uires cosmetic changes None of the above $ns% 3 /1 Bow different is Tester when com ared to . such as rocessing s eed. 3. #.eve!o er 1Tester :s aim is to find fau!t. . #. #. resource consum tion.oing the errors systematica!!y 2ogica! errors <rrors found because of wrong synta" None of the above $ns% /9 2 What are the !ow !eve! bugs. 2. 2. 2. 2. 21oth the )o!es are same 3Tester is res onsib!e for the bugs he found. . +erformance and 2oad Tests . 1. 3.

1Ma-ing two e*ua! arts 2Test the roduct using any va!ue in a grou . which re resents the entire grou 3Testing the roduct with a!! the va!ues in a grou of va!ues #None of the above 2 // We re*uire Test +!ans to @(((((((@ 1To conduct the testing in a systematic way 2because it is s ecified in the ro4ect !an 3It is art of S.efect 2og is !in-ed 1'nit Testing 2Integration Testing 3System I $cce tance Testing #$!! the above # 32 What is automated testing 1$utomated testing is rocess of automating the manua! testing rocess 2$utomated testing is the rocess of using a set of com uter rograms to rovide test in ut to other rograms.. .ifficu!t to say #None of the above 2 /8 Which of the fo!!owing is true 1Testing begins .and continues throughout the ro4ect 2Testing is ossib!e on!y after coding is com !ete 3Testing starts on!y after de!ivering the roduct to customer #Testing starts at System Tesing hase 1 31 To which hase the .eve!o ment +ro4ects on!y 3)e6<ngineering +ro4ects on!y #$!! the above # /7 Testing re resents the u!timate review of system s ecification. design and coding 1T)'< 20$2S< 3. and to automatica!!y verify the resu!ts of the test.ay ?ne on a ro4ect.2> #None of the above 1 /3 Tester )o!e can be assigned to 1Team member on!y 2Modu!e !eader a!so 3+ro4ect 2eader #$!! the above # /5 We do testing in 1Maintenance +ro4ects on!y 2.#$!! the above # /3 We can use mannua! Testing a roach in the fo!!owing situations 1?ne6time testing 2Tests with redictab!e resu!ts 3If it is not an $d hoc=random testing #None of the above 1 /# <*uiva!ence artitioning: in testing is.

2@. 8888 and 19999.@ 3Testing conducted to eva!uate the wor-ing condition of the tester #$!! of the above 2 3/ $ Metric is a @(((((((((@ 1$ measurement in meters 2$ numerica! va!ues measured in meters 3is a measurement function #None of the above 3 33 $ software *ua!ity metric is @(((((((@ 1$ metric which has a degree of *ua!ity 2@$ function whose in uts are software data and whose out ut is a sing!e numerica! va!ue that can be inter reted as the degree to which software ossesses a given attribute that affects its *ua!ity. +!ease s ecify that a!! these cases fa!! under which category@ 11oundary Ca!ue $na!ysis 2<*uiva!ence +artitioning 3$! ha Testing #1eta Testing 1 59 Which one of the be!ow is true with regard to 'NIT T<STINJ.@@ 31oth D$% and D1% #None of the above 2 35 @$ Test >ase is a @@(((((((((((@@ 1Test cases are the s ecific in uts and the rocedures that we fo!!ow when you test the software.e technica! su ort costs 3Be! managers ma-e shi =no shi decisions #$!! of the above # 38 @I am bui!ding testcases for a rogram.remature rodcut re!eases 20ind defects and minimi.If I bui!d # testcases with the in ut va!ues 9999. 1modu!e interface I !oca! data structure 21oundary conditions 3inde endent aths I error6hand!ing aths . and a set of e"ecution conditions for a test item. redicted resu!ts.3It is the rocess of testing an automated system #$!! of the above 2 33 The fo!!owing are the benefits from test automation& 1Im roved software *ua!ity 2)educed testing resource D eo !e% re*uirements. trans!ating into direct cost savings 3Jreater user satisfaction #$!! the above # 3# Stress Testing is @((((((((@ 1The tester is wor-ign under stress to test the system 2@Testing conducted to eva!uate a system or com onent at or beyond the !imits of its s ecified re*uirements with the goa! of causing the system to fai!.@ 31oth D$% and D1% #None of the above 3 37 The ob4ective of testing is to 11!oc. 9991.ocumentation s ecifying in uts. The rogram shou!d acce t data in the range 9991 thru 8888.

2The aim is to verify a!! system e!ements and va!idate conformance against S)S. beginning with the main contro! modu!e 1 5/ Which one of the fo!!owing is N?T re!ated to the System Testing 1>om atibi!ity = >onversion Testing 2.ocumentation Testing 30aci!ity Testing I +erformance Testing #1ottom6' I To . 1T)'< 20$2S< 3I am not sure #I am b!an1 53 Which one of the be!ow is N?T true with regard to SEST<M T<STINJ.own Testing # 55 'sabi!ity Testing is done during 1System Testing 2Integration Testing 3'nit Testing #None of the above 1 57 )ecoverty I )e!iabi!ity Testing is done during 1System Testing 2Stress Testing 3+erformance Testing #'nit Testing 1 58 $cce tance test is conducted to va!idate 6666666 1S)S 2'). the combination is in correct = inconsistent #Modu!es are integrated by moving downward through the contro! hierarchy.#$!! the above # 51 Which one of be!ow is T)'< with regard to Integration Testing 11!ac-6bo" test case design techni*ues are the most reva!ent during Integration Testing 2Whi!e6bo" test case design techni*ues are the most reva!ent during Integration Testing 3We use no techni*ues during Integration Testing #We test for the synta" va!idity during the Integration Testing 1 52 )egression testing is the re6e"ecution of some subset of tests that have a!ready been conducted to ensure that changes have not ro agated unintended side effects. $nd the aim is to verify a!! system e!ements and va!idate conformance against S)S 2we verify the software structure whi!e conducting tests to uncover errors associated with modu!e interfacing 3testing is done to show that even though com onents were individua!!y satisfactory. # 5# Which one of the fo!!owing is re!ated to the System Testing 1We test ?vera!! System 0unction and erformance.efinition . 3System testing is aimed at revea!ing bugs that can not be attributed to a com onent as such. to inconsistencies between com onents or !anned interactions between com onents. 3+rob!em . 1System testing verifies that a!! e!ements mesh ro er!y and the overa!! system function= erformance is achieved. #System testing verifies that the synta" of the source code is ro er for a!! the units.

2. 2. ?versight <ducationa! Transcri tion Interface $ns% # . 1oth #. Synta" .efect Ty e 1.ocumentation 0unction >ommunication $ns% 73 # Which one of the be!ow is not a >$'S< category. #. 1. #. 2. 3.#None of the above 2 79 Which one of the fo!!owing is true with regard to )egression Testing 1. 3. #. )e6e"ecution of some subset of tests that have a!ready been conducted to ensure that changes have not ro agated unintended side effects 2. 3. Testing after changes have been made to ensure that no unwanted changes were introduced 3. We get bugs during 'nit I Integration Testing We get bugs during System Testing We get bugs during $cce tance Testing $!! the above $ns% 71 $ns% 72 # Which one of the fo!!owing is not a . None of the above 2 )egression testing is recommended in case 66666 1.