istqb foundation sample question paper no 22 to 27

8/9/2019 ISTQB Foundation Sample Question Paper No 22 to 27

1/33

ISTQB Foundation Sample Question Paper No. 22Q. 1: Test planning has which of the following major tasks?i. Determining the scope and risks, and identifying the objectives of testing.ii. Determining the test approach techni!"es,test items, coverage, identifying and interfacing theteams involved in testing , testware#

iii. $eviewing the Test %asis s"ch as re!"irements,architect"re,design,interface#iv. Determining the e&it criteria.

A. i,ii,iv are true and iii is falseB. i,,iv are true and ii is falseC. i,ii are true and iii,iv are falseD. ii,iii,iv are true and i is false

Q. 2: Deciding How much testing is enough should take into account :-i. Level of Risk including Technical and Business poduct and po!ect iskii. "o!ect constaints such as time and #udgetiii. $i%e of Testing Teamiv. $i%e of the Development Team

A. i,ii,iii are true and iv is falseB. i,,iv are true and ii is falseC. i,ii are true and iii,iv are falseD. ii,iii,iv are true and i is false

Q. &: 'hich of the following will #e the #est definition fo Testing:A. The goal / purpose of testing is to demonstrate that the program works.B. The purpose of testing is to demonstrate that the program is defect free.C. The purpose of testing is to demonstrate that the program does what it is supposed todo.D. Testing is executing Software for the purpose of finding defects.

Q. (: )inimum Tests Re*uied fo $tatement +oveage and Banch +oveage:Read " Read Q ,f p* /00 then"int 1Lage1 nd if ,f p 30 then "int 1pLage1 nd if

A. Statement coverage is , Branch Coverage is B. Statement coverage is ! and "ranch coverage is C. Statement coverage is # and "ranch coverage is D. Statement Coverage is $ and Branch coverage is

Q. 3: )atch eve4 stage of the softwae Development Life c4cle with the Testing Life c4cle:i. Hi-level design a 5nit tests ii. +ode # 6cceptance tests

iii. Low-level design c $4stem testsiv. Business e*uiements d ,ntegation tests

A. i%d , ii%a , iii%c , iv%"B. i%c , ii%d , iii%a , iv%"C. i%" , ii%a , iii%d , iv%cD. i%c , ii%a , iii%d , iv%"

Q. 7: 'hich of the following is a pat of Test +losue 6ctivities8


2/33

i. +hecking which planned delivea#les have #een deliveedii. Defect epot anal4sis.iii. 9inali%ing and achiving testwae.iv. 6nal4%ing lessons.

A. i , ii , iv are true and iii is false

B. i , ii , iii are true and iv is falseC. i , iii , iv are true and ii is falseD. All of a"ove are true

Q. : 'hich of the following is ;


3/33

A. D)namic anal)sis toolB. Static Anal)sis tool.C. 3aintenance tool.D. Configuration tool.

Q. /3: +4clomatic comple>it4 is used to calculate

A. 8um"er of independent paths in the "asis set of a programB. 8um"er of "inar) decisions 9 #C. 8um"er "ound for the num"er of tests that must "e conducted to ensure that allstatements have "een executed at least onceD. 8um"er of "ranches and decisions

Q. /7: 'hich of the following is not included in Test "lan.A. &eatures to "e tested.B. 'nvironmental needs.C. Suspension criteria.D. 'xpected results.

Q. /: $oftwae *ualit4 is not elevant toA. CorrectnessB. 5sa"ilit)C. :ia"ilit)D. 2eusa"ilit).

Q. /=: )atch the following: /. Test estimation 2. Test contol &. Test monitoing a. )easues of tacking pocess #. ffot e*uied to pefom activities c. Reallocation of esouces

A. #%", %c, !%a

B. #%", %a, !%cC. #%c, %a, !%"D. #%a, %", !%c

Q. /C: 'hen do 4ou stop testing8A. ;hen the specified num"er of faults are found.B. ;hen the test completion criteria are met.C. ;hen all high and medium priorit) tests are complete.D. ;hen all statements have "een executed

Q. 20: 'hat is the smallest num#e of test cases e*uied to "ovide /00A #anch coveage8

,f@>4 >E>/F

else 4E4/Fwhile@>4G4E>4F >E>/FI

A. #B. C. !


4/33

D. $

Q. 2/: )atch the following./. +onfiguation identification2. +onfiguation contol&. $tatus epoting

(. +onfiguation auditinga. )aintains of +,Js in a li#a4#. +hecks on the contents of the li#a4c. 9unction ecoding and tacking po#lems.d. Re*uies the all +,Js and thei vesions in the s4stem ae known

A. #%d, %c, !%d, $%a. B. #%d, %a, !%c, $%". C. #%a, %", !%d, $%c. D. #%c, %", !%a, $%d.

Q. 22: ,ntegation testing in the lage involves:A. Testing the s)stem when com"ined with other s)stems.B. Testing a su"%s)stem using stu"s and drivers.C. Testing a s)stem with a large num"er of users.D. Com"ing software components and testing them in one go.

Q. 2&: testing as pe B$C23-,,standads.A. 2andom testingB. Data &low testing.C. Statement testing.D. S)ntax testing.

Q. 2(: 6 piece of softwae has #een given what tests in the 9ollowing will 4ou pefom8/ Test the aeas most citical to #usiness pocesses2 Test the aeas whee faults will #e ma>imum& Test the easiest functionalities

A. #Q. 23: 'hich of the following is a t4pe of non-functional testing8A. 5sa"ilit) testing.B. Statement Coverage.C. Dataflow testing.D. Cause%effect graphing.

Q. 27: 'hat t4pe of testing will 4ou pefom on intenet #anking solution8A. S)stem integration

B. &unctional testingC. 8on%functional testing.D. 2e(uirements testing

Q. 2: 'hich of the following ae false8A. 7ncidents should alwa)s "e investigated and resolved.B. 7ncidents occur when expected and actual results differ.C. 7ncidents can "e anal)=ed to assist in test process improvement.D. An incident can "e raised against documentation.


5/33

Q. 2=: Testing is not done toA. &ind faultsB. 7mprove (ualit)C. Check user friendliness.D. 7mprove software accurac)

Q. 2C: 6 field failue occus when multiple uses access a s4stem. 'hich of the following is tue8A. This is an accepta"le risk of a multi%user s)stem.B. 7nsufficient functional testing has "een performed.C. This indicates an important non%functional re(uirement was not specified and tested.D. 7t is not possi"le to test against such events prior to release.

Q. &0: "eople who donJt paticipate in technical eviewsA. Anal)stsB. 3anagementC. DevelopersD. Testers

Q. &/: 'hat is failue8A. Deviation from expected result to actual resultB. Defect in the software.C. 'rror in the program code. D. &ault in the s)stem.

Q. &2: >clusive use of white #o> testing in a test-phase will:A. 'nsure the test item is ade(uatel) tested.B. 3ake the need for "lack%"ox testing redundant.C. 2un the risk that the re(uirements are not satisfied.D. Suffices for the unit testing phase.

Q. &&: 'hich of the following is least impotant in test management8A. 'stimating test duration.B. 7ncident 3anagement.C. Configuration 3anagement.

D. De%"ugging.

Q. &(: 6 standad fo softwae testing teminolog4 is:A. 7''' 0+.##B. 7S> -++#C. BS -*%#D. BS -*%

Q. &3: 'hich of the following is ;


6/33

A. 2egression testing.B. 7ntegration testing.C. 'rror 6uessingD. S)stem testing.

Q. &=: To make a test effective it is most impotant that:

A. 7t is eas) to execute.B. 7t is designed to detect faults if present.C. The expected outcome is specified "efore execution.D. 7t is unlikel) to dela) progress.

Q. &C: o guessing is:A. An appropriate wa) of deriving s)stem tests.B. >nl) used if good re(uirements are not availa"le.C. >nl) used when good re(uirements are availa"le.D. The most appropriate wa) of deriving s)stem tests.

Q. (0: 6mount of testing pefomed will not depend onA. 2isks involvedB. Contractual re(uirementsC. ?egal re(uirementsD. Test data.

6nswes:@.#%A @.%C @.!%D @.$%C@.*%D @.%C @.%C @.0%[email protected]%A @.#+%A @.##%C @.#%C@.#!%D @.#$%A @.#*%B @.#%D@.#%C@.#0%A@.#-%B@.+%B@.#%B

@.%A@.!%D@.$%A@.*%A@.%C@.%[email protected]%[email protected]%C@.!+%B@.!#%A@.!%C@.!!%D@.!$%C

@.!*%A@.!%D@.!%C@.!0%C@.!-%D@.$+%D


7/33

ISTQB Foundation Sample Question Paper No. 23

Q. /: 9o softwae to #e elia#le it must:A. Be eas) to maintain.B. Be unlikel) to cause a failure.C. 8ever fail under an) circumstances.

D. Be written according to coding standards

Q. 2: ,n as4stem designed to wok out the ta> to #e paid: 6n emplo4ee has (000 of sala4 ta> fee. The ne>t /300 is ta>ed at /0A Thene>t 2=000 is ta>ed at 22A 6n4 futhe amount is ta>ed at (0A To the neaest which of these is a valid Bounda4 Kalue 6nal4sis testcase8A. #*++B. !++#C. 0+++D. !!*+#

Q. &: 9aults found #4 uses ae due to:A. 4oor (ualit) software

B. 4oor software and poor testingC. Bad luckD. 7nsufficient time for testing

Q. (: 6n incident logging s4stemA. >nl) records defectsB. 7s of limited valueC. 7s a valua"le source of proect information during testing if it contains all incidentsD. Should "e used onl) ") the test team.

Q. 3: The late in the development life c4cle a fault is discoveed? the moe e>pensive it is to fi>.'h48A. The documentation is poor, so it takes longer to find out what the software is doing.

B. ;ages are risingC. The fault has "een "uilt into more documentation, code, tests, etc.D. 8one of the a"ove

Q. 7: 'hich of the following is tue8A. Component testing should "e "lack "ox, s)stem testing should "e white "ox.B. 7f u find a lot of "ugs in testing, )ou should not "e ver) confident a"out the (ualit) of softwareC. The fewer "ugs )ou find, the "etter )our testing wasD. The more tests )ou run, the more "ugs )ou will find.

Q. : ,f the pseudo code #elow wee a pogamming language ?how man4 tests aee*uied to achieve /00A statement coveage8/. ,f >E& then

2. Displa4messageMF&. ,f 4E2 then(. Displa4messageNF3. lse7. Displa4messageOF. lse=. Displa4messageOF

A. #B. C. ! D. $


8/33

Q. =: $oftwae testing activities should statA. As soon as the code is writtenB. During the design stageC. ;hen the re(uirements have "een formall) documentedD. As soon as possi"le in the development life c)cle

Q. C: 5sing the same code e>ample as *uestion /?how man4 tests ae e*uied to achieve /00A #anchPdecision coveage8A. #B. C. !D. $

Q. /0: 6 test design techni*ue isA. A process for selecting test casesB. A process for determining expected outputsC. A wa) to measure the (ualit) of softwareD. A wa) to measure in a test plan what has to "e done

Q. //: 'hat is the main eason fo testing softwae #efoe eleasing it8A. To show that s)stem will work after releaseB. To decide when the software is of sufficient (ualit) to releaseC. To find as man) "ugs as possi"le "efore releaseD. To give information for a risk "ased decision a"out release

Q. /2: Testwae@test cases? test datasetA. 8eeds configuration management ust like re(uirements, design and codeB. Should "e newl) constructed for each new version of the softwareC. 7s needed onl) until the software is released into production or useD. Does not need to "e documented and commented, as it does not form part of thereleased software s)stem

Q. /&: 'hich of the following is ;


9/33

A. Design "asedB. Big%"angC. Bottom%upD. Top%downQ. /: 'hich of the following tools would 4ou use to detect a memo4 leak8A. State anal)sis

B. Coverage anal)sisC. D)namic anal)sisD. 3emor) anal)sis

Q. /=: 'hich of the following statements ae tue8A. &aults in program specifications are the most expensive to fix.B. &aults in code are the most expensive to fix.C. &aults in re(uirements are the most expensive to fixD. &aults in designs are the most expensive to fix.

Q./C: ,nceasing the *ualit4 of the softwae? #4 #ette development methods? will affect the time needed fo testing @the test phases #4:A. 2educing test timeB. 8o changeC. 7ncreasing test timeD. Cant sa)

Q. 20: 'hich of the following is a #lack #o> design techni*ue8A. Statement testingB. '(uivalence partitioningC. 'rror% guessingD. 5sa"ilit) testing

Q. 2/: 'hen epoting faults found to developes? testes should #e:A. As polite, constructive and helpful as possi"leB. &irm a"out insisting that a "ug is not a EfeatureE if it should "e fixedC. Diplomatic, sensitive to the wa) the) ma) react to criticismD. All of the a"ove

Q. 22: 'hich of the following statements is not tueA. 4erformance testing can "e done during unit testing as well as during the testing of whole s)stemB. The acceptance test does not necessaril) include a regression testC. :erification activities should not involve testers reviews, inspections etcD. Test environments should "e as similar to production environments as possi"le

Q. 2&: 'hat is the impotant citeion in deciding what testing techni*ue to use8A. Fow well )ou know a particular techni(ueB. The o"ective of the testC. Fow appropriate the techni(ue is for testing the application

D. ;hether there is a tool to support the techni(ue

Q. 2(: 'hen should 4ou stop testing8A. ;hen time for testing has run out.B. ;hen all planned tests have "een runC. ;hen the test completion criteria have "een metD. ;hen no faults have "een found ") the tests run

Q. 23: +oveage measuement


10/33

A. 7s nothing to do with testingB. 7s a partial measure of test thoroughnessC. Branch coverage should "e mandator) for all softwareD. Can onl) "e applied at unit or module testing, not at s)stem testing

Q. 27: 'hich of the following is ;it4 is almost likel4 to #e:A. ?argeB. SmallC. Difficult to writeD. Difficult to test

Q. &2: 'hich of the following is the odd one out8A. ;hite "ox

B. 6lass "oxC. StructuralD. &unctional

Q. &&: 'hich of the following techni*ues ae #lack #o> techni*ues8A. State transition testing, code testing, agile testingB. '(uivalence partitioning, state transition testing, decision ta"le testingC. S)stem testing, acceptance testing, e(uivalence partitioningD. S)stem integration testing, s)stem testing, decision ta"le testing


11/33

Q. &(: 6 num#e of citical #ugs ae fi>ed in softwae. 6ll the #ugs ae in one module?elated to epots. The test manage decides to doegession testing onl4 on the epots module.A. The test manager should do onl) automated regression testing.B. The test manager is ustified in her decision "ecause no "ug has "een fixed in other modulesC. The test manager should onl) do confirmation testing. There is no need to do regression testing

D. 2egression testing should "e done on other modules as well "ecause fixing one module ma) affect other modules

Q. &3: 'hich of the following statements contains a valid goal fo a functional test set8A. A goal is that no more failures will result from the remaining defectsB. A goal is to find as man) failures as possi"le so that the cause of the failures can "eidentified and fixedC. A goal is to eliminate as much as possi"le the causes of defectsD. A goal is to fulfil all re(uirements for testing that are defined in the proect plan.

Q. &7: 'hat makes an inspection diffeent fom othe eview t4pes8A. 7t is led ") a trained leader, uses formal entr) and exit criteria and checklistsB. 7t is led ") the author of the document to "e inspectedC. 7t can onl) "e used for reviewing design and codeD. 7t is led ") the author, uses checklists, and collects data for improvement

Q. &: 'h4 does the #ounda4 value anal4sis povide good test cases8A. Because it is an industr) standardB. Because errors are fre(uentl) made during programming of the different cases near theGedges of the range of valuesC. Because onl) e(uivalence classes that are e(ual from a functional point of view are considered in the test casesD. Because the test o"ect is tested under maximal load up to its performance limits

Q. &=: ,f a pogam is tested and /00A #anch coveage is achieved? which of the following coveage citeia is then guaanteed to #eachieved8A. #++H '(uivalence class coverage

B. #++H Condition coverage and #++H Statement coverageC. #++H Statement coverageD. #++H 3ultiple condition coverage

Q. &C: 6 defect management s4stem shall keep tack of the status of eve4 defectegisteed and enfoce the ules a#out changing thesestates. ,f 4ou task is to test thestatus tacking? which method would #e #est8A. ?ogic%"ased testingB. 5se%case%"ased testingC. State transition testingD. S)stematic testing according to the :%model

Q. (0: ,n s4stem testing...

A. Both functional and non%functional re(uirements are to "e testedB. >nl) functional re(uirements are tested1 non%functional re(uirements are validated in areviewC. >nl) non%functional re(uirements are tested1 functional re(uirements are validated in a reviewD. >nl) re(uirements which are listed in the specification document are to "e tested6nswes: @.#%B @.%D @.!%B @.$%C @.*%C @.%B @.%C @.0%D @.-%C @.#+%A @.##%D @.#%A @.#!%B @.#$%A@.#*%B @.#%A @.#%C @.#0%C @.#-%A @.+%B @.#%D @.%C @.!%B @.$%C @.*%B @.%A @.%D @.0%[email protected]%B @.!+%A @.!#%D @.!%D @.!!%B @.!$%D @.!*%B @.!%A @.!%B @.!0%B @.!-%C @.$+%A


12/33


Q. /: ,ntegation testing has following chaacteistics7. 7t can "e done in incremental manner77. 7t is alwa)s done after s)stem testing777. 7t includes functional tests

7:. 7t includes non%functional tests

A. 7, 77 and 777 are correctB. 7 is correctC. 7, 777 and 7: are correct

Q. 2: 'hich of the following activities diffeentiate a walkthough fom a fomal eview8A. A walkthrough does not follow a defined processB. &or a walkthrough individual preparation ") the reviewers is optionalC. A walkthrough re(uires meetingD. A walkthrough finds the causes of failures, while formal review finds the failures

Q. &: 'h4 is testing necessa48

A. Because testing is good method to make there are not defects in the softwareB. Because verification and validation are not enough to get to know the (ualit) of the softwareC. Because testing measures the (ualit) of the software s)stem and helps to increase the (ualit)D. Because testing finds more defects than reviews and inspections.'. 7, 77 and 7: are correct

Q. (: ,n foundation level s4lla#us 4ou will find the main #asic pinciples of testing.'hich of the following sentences desci#es one ofthese #asic pinciples8A. Complete testing of software is attaina"le if )ou have enough resources and test toolsB. ;ith automated testing )ou can make statements with more confidence a"out the (ualit) of a product than with manual testing

C.&or a software s)stem, it is not possi"le, under normal conditions, to test all input and output com"inations.D. A goal of testing is to show that the software is defect free.

Q. 3: 'hich of the following is tueA. Testing is the same as (ualit) assuranceB. Testing is a part of (ualit) assuranceC. Testing is not a part of (ualit) assuranceD. Testing is same as de"ugging

Q. 7: This pat of a pogam is given:;F7?' condition A

Do B'8D ;F7?'Fow man) decisions should "e tested in this code in order to achieve #++H decision coverageIA. B. 7ndefiniteC. #D. $

Q. : ,n a flight esevation s4stem? the num#e of availa#le seats in each planemodel is an input. 6 plane ma4 have an4 positive num#eof availa#le seats? up to the


13/33

given capacit4 of the plane. 5sing Bounda4Kalue anal4sis? a list of availa#le seat values wee geneated.'hich of the following lists is coect8A. #, , capacit) %#, capacit), capacit) plus #B. +, #, capacit), capacit) plus #C. +, #, , capacit) plus #, a ver) large num"er

D. +, #, #+, #++, capacit), capacit) plus one

Q. =: 'hich of the following is a valid collection of e*uivalence classes fo the following po#lem:6n intege field shall contain valuesfom and including / to and including /3A. ?ess than #, # through #*, more than #*B. 8egative num"ers, # through #*, a"ove #*C. ?ess than #, # through #$, more than #*D. ?ess than +, # through #$, #* and more

Q. C: 'hich of the following is coect a#out static anal4sis toolsA. The) help )ou find defects rather than failuresB. The) are used ") developers onl)C. The) re(uire compilation of codeD. The) are useful onl) for regulated industries

Q. /0: 'hich of the following is most often consideed as components inteface #ug8A. &or two components exchanging data, one component used metric units, the other oneused British unitsB. The s)stem is difficult to use due to a too complicated terminal input structureC. The messages for user input errors are misleading and not helpful for understanding theinput error causeD. 5nder high load, the s)stem does not provide enough open ports to connect to

Q. //: 'hich of the following is coect a#out static anal4sis tools8A. Static anal)sis tools are used onl) ") developersB. Compilers ma) offer some support for static anal)sisC. Static anal)sis tools help find failures rather than defectsD. Static anal)sis tools re(uire execution of the code to anal)=e the coverage

Q. /2: 'hich of the following list contains onl4 non-functional tests8A. 7nteropera"ilit) compati"ilit) testing, relia"ilit) testing, performance testingB. S)stem testing, performance testingC. ?oad testing, stress testing, component testing, porta"ilit) testingD. Testing various configurations, "eta testing, load testing

Q. /&: 'hich set of metics can #e used fo monitoing of the test e>ecution8A. 8um"er of detected defects, testing cost1B. 8um"er of residual defects in the test o"ect.C. 4ercentage of completed tasks in the preparation of test environment1 test casesprepared

D. 8um"er of test cases run / not run1 test cases passed / failed

Q. /(: 'hat test items should #e put unde configuation management8A. The test o"ect, the test material and the test environmentB. The pro"lem reports and the test materialC. >nl) the test o"ect. The test cases need to "e adapted during agile testingD. The test o"ect and the test material

Q. /3: This pat of a pogam is given:


14/33

'H,L @condition 6Do B;D 'H,L

How man4 paths should #e tested in this code in ode to achieve /00A path coveage8

A. >neB. 7ndefiniteC. TwoD. &our

Q. /7: 'hat is the pupose of test e>it citeia in the test plan8A. To specif) when to stop the testing activit)B. To set the criteria used in generating test inputsC. To ensure that the test case specification is completeD. To know when a specific test has finished its execution

Q./:,f a pogam is tested and /00A condition coveage is achieved? which of the following coveage

citeia is then guaanteed to #eachieved8A. #++H "ranch coverageB. #++H condition coverage and #++H statement coverageC. '(uivalence class and "oundar) value coverageD. 8o other white "ox coverage criterion is guaranteed to "e fulfilled #++H

Q. /=: 'hich of the following can #e oot cause of a #ug in a softwae poduct8@, The po!ect had incomplete pocedues fo configuation management.@,, The time schedule to develop a cetain component was cut.@,,, the specification was unclea@,K 5se of the code standad was not followed up@K The testes wee not cetified

A. 7 and 77 are correctB. 7 through 7: are correctC. 777 through : are correctD. 7, 77 and 7: are correct

Q./C: The following list contains isks that have #een identified fo a softwae poduct to #e developed. 'hich of these isks is ane>ample of a poduct isk8A. 8ot enough (ualified testers to complete the planned testsB. Software deliver) is "ehind scheduleC. Threat to a patients lifeD. !rd part) supplier does not suppl) as stipulated

Q. 20: 'hich of the following statements is coect8A. Static anal)sis tools produce statistics during program executionB. Configuration management s)stems allow us to provide accurate defectstatistics of different configurationsC. Stress testing tools examine the "ehavior of the test o"ect at or "e)ond full loadD. 4erformance measurement tools can "e used in all phases of software life%c)cle

Q. 2/: 'hich of the following po!ect inputs influence testing8@, +ontactual e*uiements@,, Legal e*uiements@,,, ,ndust4 standads


15/33

@,K 6pplication isk@K "o!ect si%eA. 7 through 777 are correctB. All alternatives are correctC. 77 and : are correctD. 7, 777 and : are correct

Q. 22: 6 test enginee is testing a Kideo "la4e @K+R? and logs the following epot:Title: 9ast 9owad stops afte 2 minutes. ,t happens eve4 time >pected esult: 9ast fowad continues till theend of the tape $eveit4: High"ioit4: 5gent

'hat impotant infomation did the enginee leave out8

A. 7dentification Software and hardware of the :C2B. Actual resultC. Fistor) of the reportD. 7deas for the test case improvement

Q. 2&: )aintenance testing is:A. Testing managementB. S)non)m of testing the (ualit) of serviceC. Triggered ") modifications, migration or retirement of existing softwareD. Testing the level of maintenance ") the vendor

Q. 2(: 'h4 is incemental integation pefeed ove 1#ig #ang1 integation8A. Because incremental integration has "etter earl) defects screening and isolation a"ilit)B. Because E"ig "angE integration is suita"le onl) for real time applicationsC. 7ncremental integration is preferred over EBig Bang 7ntegrationE onl) for E"ottom upEdevelopment modelD. Because incremental integration can compensate for weak and inade(uate component testing

Q. 23: K-)odel is:A. A software development model that illustrates how testing activities integrate withsoftware development phasesB. A software life%c)cle model that is not relevant for testingC. The official software development and testing life%c)cle model of 7ST@BD. A testing life c)cle model including unit, integration, s)stem and acceptance phases

Q. 27: 'hich of the following items need not to #e given in an incident epot8A. The version num"er of the test o"ectB. Test data and used environmentC. 7dentification of the test case that failedD. The location and instructions on how to correct the fault

Q. 2: Test data planning essentiall4 includesA. 8etworkB. >perational 3odelC. Boundar) value anal)sisD. Test 4rocedure 4lanning

Q. 2=: 6cceptance testing meansA. Testing performed on a single stand J alone module or unit of codeB. Testing after changes have "een made to ensure that no unwanted changes were introducedC. Testing to ensure that the s)stem meets the needs of the organi=ation and end user.


16/33

D. 5sers test the application in the developers environment

Q.2C: The testing should include opeational tests of the new envionment as well as of thechanged softwaeA. S)stem Testing

B. 7ntegration testingC. Component testingD. 3aintenance testing

Q. &0: 6 isk-#ased appoach to testing povides poactive oppotunities to educe the levels ofpoduct isk? stating in the initial stages of a po!ectA. TrueB. &alse

Q. &/: 9unctional testing is mostl4A. :alidation techni(uesB. :erification techni(uesC. Both of the a"ove

D. 8one of the a"ove

Q. &2: Banch +oveageA. Another name for decision coverageB. Another name for all%edges coverageC. Another name for "asic path coverageD. All the a"ove

Q.&&: The ,s the activit4 whee geneal testing o#!ectives ae tansfomed into tangi#le test conditions and test designsA. Testing 4lanningB. Test ControlC. Test anal)sis and designD. Test implementation

Q. &(: ,ntegation testing whee no incemental testing takes place pio to all thes4stemJs components #eing com#ined to fom thes4stem.A. S)stem testingB. Component TestingC. 7ncremental TestingD. Big "ang testing

Q.&3: 6 test case design techni*ue fo a component in which test cases ae designed to e>ecute statements is called as8A. State transition Testing

B. Static TestingC. Transition testingD. Statement testing

Q. &7: 'ho should have technical and Business #ackgound.A. 3oderatorB. AuthorC. 2eviewerD. 2ecorder


17/33

Q. &: 6 test plan definesA. ;hat is selected for testingB. >"ectives and resultsC. 'xpected resultsD. Targets and misses

Q. &=: +omponent integation testing can #e doneA. Before 7ntegration testingB. After unit testingC. After component testingD. After s)stem testing

Q. &C: Test #asis documentation is anal4%ed in which phase of testingA. Test Anal)sisB. Test DesignC. Test 'xecutionD. Test 4lanning

Q. (0: 'hich one is not the task of test leade8A. Coordinate the test strateg) and plan with proect managers and othersB. Decide a"out the implementation of the test environmentC. ;rite test summar) reportsD. 2eview and contri"ute to test plans

6nswes:@.#%C @.%B @.!%C @.$%C@.*%B @.%A @.%B @.0%[email protected]%A @.#+%A @.##%B @.#%C@.#!%D @.#$%A @.#*%C @.#%A@.#%B@.#0%B@.#-%C

@.+%C@.#%B@.%A@.!%C@.$%A@.*%A@.%D@.%[email protected]%[email protected]%D@.!+%A@.!#%A@.!%A

@.!!%C@.!$%D@.!*%D@.!%C@.!%B@.!0%C@.!-%A@.$+%D


18/33


Q. /: if @condition/ @condition2 function/@statement/Felse statement2FA. Decision coverage

B. Condition coverageC. Statement coverageD. 4ath Coverage

Q. 2: eviews ae often held with !ust the pogamme who wote the code and one o two othe pogammes o testes.A. &ormal 2eviewsB. 4eer 2eviewsC. Semi%&ormal 2eviewsD. All of the a"ove

Q. &: ,n testing test cases i.e input to the softwae ae ceated #ased on the specifications languages

A. State Transition TestingB. 2andom TestingC. S)ntax TestingD. 4enetration testing

Q. (: 'hite Bo> TestingA. Same as glass "ox testingB. Same as clear "ox testingC. Both A. and B.D. 8one of the a"ove.

Q. 3: Keification activities duing design stages aeA. 2eviewing and 7nspecting

B. 7nspecting and TestingC. 2eviewing and TestingD. 2eviewing, 7nspecting and Testing.

Q. 7: *uivalence patitioning consists of vaious activities:A. 'nsure that test cases test each input and output e(uivalence class at least onceB. 7dentif) all inputs and all outputsC. 7dentif) e(uivalence classes for each inputD. All of the a"ove

Q. : $tatic 6nal4sisA. Same as static testingB. Done ") the developers

C. Both A. and BD. 8one of the a"ove

Q. =: $i%e of a po!ect is defined in tems of all the following e>ceptA. 4erson da)sB. 4erson hoursC. Calendar monthsD. 8one of the a"ove

Q. C: Testing esponsi#ilities:


19/33

Teste / Keif4 that the pogamis a#le to displa4 images cleal4 on all /0 of the monitos in the la#Teste 2 - )ake sue the pogam instuctions ae eas4 to use $ecuit4 concens aeimpotant fo which t4pe of applicationsTeste & Keif4 that the calculation module woks coectl4 #4 using #oth scipts and adhoc testing. 'hich tem is used to efe to thetesting that is pefomed #4

Teste & in the a#ove scenaio8A. 5nit testingB. Algorithm specific testingC. Compati"ilit) testingD. Black "ox testing

Q. /0:


20/33

Q. /: Risk anal4sis talks a#outA. The data re(uired for testing, the infrastructure re(uirements to manage the data as well as the methods for preparing test data,re(uirements, converters and sources

B. Details what t)pes of tests must "e conducted, what stages of testing are re(uired and outlines these(uence and timing of tests

C.A testing goal. 7t is a statement of what the tester is expected to accomplish or validate during a testing activit). These guide the developmentof test cases and proceduresD. 8one of the a"ove

Q. /=: 'hat ae the 2 ma!o components taken into consideation with isk anal4sis8A. The pro"a"ilit) the negative event will occurB. The potential loss or impact associated with the eventC. Both A. and B.D. 8either A. nor B.

Q./C: ,f the application is comple>? #ut ;ing defects found t4picall4 done #4A. 3oderatorB. AuthorC. 2eviewerD. 2ecorder

Q. 2&: The ma4 facilitate the testing of components o pat of a s4stem #4simulation the envionment in which the test o#!ect will unA. Test Design toolB. Test data preparation toolC. Test execution toolD. Test harness'. 8one of the a"ove

Q. 2(: Regession testing mainl4 helps inA. 2e%testing fixed defectsB. Checking for side%effects of fixesC. Checking the core gapsD. 'nsuring high level sanit)


21/33

Q. 23: Review is one of the methods of KK. The othe methods aeA. 7nspectionB. ;alkthroughC. TestingD. All of the a"ove

Q. 27: 'hich eview is ine>pensiveA. 7nformal 2eviewB. ;alkthroughC. Technical reviewD. 7nspection

Q. 2: 9ollowing ae some of the testing isksA. Budget, Test environmentB. Budget, 8um"er of (ualified test resourcesC. Budget, 8um"er of (ualified test resources, Test environmentD. 8one of the a"ove

Q. 2=: Random TestingA. 4rogram is tested randoml) sampling the input.B. A "lack%"ox testing techni(ueC. Both A. and B.D. 8one of the a"ove.

Q. 2C: Black-#o> testing techni*ue is also called as stuctue #ased techni*ueA. TrueB. &alse

Q. &0: Relia#ilit4? usa#ilit4? efficienc4 aeA. &unctional characteristicsB. 8onfunctional characteristicsC. Both A. < B.D. 8one of the a"ove

Q. &/: Test "lanA. 2oad map for testingB. Tells a"out the actual results and expected resultsC. Both a and "D. 8one of the a"ove

Q. &2: 5se 6cceptance TestingA. Same as Alpha TestingB. Same as Beta TestingC. Com"ination of Alpha and Beta TestingD. 8one of the a"ove

Q. &&: "ath coveage includesA. Statement coverageB. Condition coverageC. Decision coverageD. 8one of these

Q. &(: 'hich testing techni*ue do 4ou pefe fo the following situations8/. $evee time pessue2. ,nade*uate specification


22/33

A. Decision testingB. 'rror guessingC. Statement testingD. 'xplorator) testing

Q. &3: Recove4 testing is a s4stem test that foces the softwae to fail and veifies that data

ecove4 is popel4 pefomed. Thefollowing should #e checked fo coectness/. Re-initiali%ation2. Restat&. Data Recove4(. +heck "oint )echanismA. # and B. #, and !C. #, , ! and $D. and $

Q. &7: Data flow anal4sis studies:A. 4ossi"le communications "ottlenecks in a program.B. The rate of change of data values as a program executes.C. The use of data on paths through the code.D. The intrinsic complexit) of the code.

Q. &: 'hich of the following is ; techni*ue8A. Statement testingB. 4ath testingC. Data flow testingD. State transition testing

Q.&=: 'hich one of the following desci#es the ma!o #enefit of veification eal4 in the life c4cle8A. 7t allows the identification of changes in user re(uirements.B. 7t facilitates timel) set up of the test environment.C. 7t reduces defect multiplication.

D. 7t allows testers to "ecome involved earl) in the proect.

Q. &C: 'hich of the following is false8A. 7n a s)stem two different failures ma) have different severities.B. A s)stem is necessaril) more relia"le after de"ugging for the removal of a fault.C. A fault need not affect the relia"ilit) of a s)stem.D. 5ndetected errors ma) lead to faults and eventuall) to incorrect "ehavior.

Q. (0: 6lpha testing is:A. 4ost%release testing ") end user representatives at the developers site.B. The first testing that is performed.C. 4re%release testing ") end user representatives at the developers site.D. 4re%release testing ") end user representatives at their sites.

6nswe:@.#%B @.%B @.!%C @.$%A @.*%A @.%A @.%C @.0%C @.-%D @.#+%C@.##%C @.#%C @.#!%D @.#$%C @.#*%D @.#%B @.#%B @.#0%C @.#-%A @.+%A@.#%B @.%B @.!%D @.$%B @.*%D @.%A @.%B @.0%A @.-%B @.!+%B@.!#%A @.!%C @.!!%D @.!$%D @.!*%C @.!%C @.!%D @.!0%C @.!-%B @.$+%C


23/33


Q. /: 'e split testing into distinct stages pimail4 #ecause:A. 'ach test stage has a different purpose.

B. 7t is easier to manage testing in stages.C. ;e can run different tests in different environments.D. The more stages we have, the "etter the testing.

Q. 2: 'hich of the following would ;


24/33

B. A minimal test set that achieves #++H path coverage will also achieve #++H statement coverage.C.A minimal test set that achieves #++H path coverage will generall) detect more faults than one that achieves #++H statement coverage.D.A minimal test set that achieves #++H statement coverage will generall) detect more faults than one t

hat achieves #++H "ranch coverage.

Q. /0: 'hich of the following statements a#out eviews is tue8A. 2eviews cannot "e performed on user re(uirements specifications.B. 2eviews are the least effective wa) of testing code.C. 2eviews are unlikel) to find faults in test plans.D. 2eviews should "e performed on specifications, code, and test plans.

Q. //: 'hat is the main diffeence #etween a walkthough and an inspection8A. An inspection is lead ") the author, whilst a walkthrough is lead ") a trained moderator.B. An inspection has a trained leader, whilst a walkthrough has no leader.C. Authors are not present during inspections, whilst the) are during walkthroughs.D. A walkthrough is lead ") the author, whilst an inspection is lead ") a trained moderator.

Q. /2: 'hich of these activities povides the #iggest potential cost saving fom the use of +6$T8A. Test managementB. Test designC. Test executionD. Test planning

Q. /&: 'hich of the following is ;


25/33

B. Can onl) "e used in component, integration and s)stem testing.C. 7s onl) performed in user acceptance testing.D. 7s not repeata"le and should not "e used.

Q. /=: ,n a s4stem designed to wok out the ta> to #e paid:6n emplo4ee has S(000 of sala4 ta> fee. The ne>t S/300 is ta>ed

at /0A The ne>t S2=000 is ta>ed at 22A6n4 futhe amount is ta>ed at (0A'hich of these goups of num#es would fall into the same e*uivalence class8A. L$0++1 L#$+++1 L0+++B. L*++1 L**++1 L0+++C. L0++#1 L!+++1 L!*+++D. L*0++1 L0+++1 L!+++

Q. /C: The oacle assumption:A. 7s that there is some existing s)stem against which test output ma) "e checked.B. 7s that the tester can routinel) identif) the correct outcome of a test.C. 7s that the tester knows ever)thing a"out the software under test.D. 7s that the tests are reviewed ") experienced testers.

Q. 20: ,n pioitising what to test? the most impotant o#!ective is to:A. &ind as man) faults as possi"le.B. Test high risk areas.C. >"tain good test coverage.D. Test whatever is easiest to test.

Q. 2/: The most impotant thing a#out eal4 test design is that it:A. 3akes test preparation easier.B. 3eans inspections are not re(uired.C. Can prevent fault multiplication.D. ;ill find all faults.

Q. 22: 6 configuation management s4stem would ;


26/33

Q. 27: Test cases ae designed duing:A. Test recording.B. Test planning.C. Test configuration.D. Test specification.

Q. 2: 6 failue is:A. &ound in the software1 the result of an error.B. Departure from specified "ehaviour.C. An incorrect step, process or data definition in a computer program.D. A human action that produces an incorrect result.

Q. 2=: How would 4ou estimate the amount of e-testing likel4 to #e e*uied8A. 3etrics from previous similar proectsB. Discussions with the development teamC. Time allocated for regression testingD. A. < B.

Q. 2C: iven the following sets of test management tems @v-%? and activit4 desciptions @/-3? which one of the following #estpais the two sets8

v - Test contolw - Test monitoing> - Test estimation4 - ,ncident management% - +onfiguation contol

/ - +alculation of e*uied test esouces2 - )aintenance of ecod of test esults& - Re-allocation of esouces when tests oveun( - Repot on deviation fom test plan3 - Tacking of anomalous test esults

A. v%!,w%,x%#,)%*,=%$B. v%,w%*,x%#,)%$,=%!C. v%!,w%$,x%#,)%*,=%D. v%,w%#,x%$,)%!,=%*

Q. &0: ,n a s4stem designed to wok out the ta> to #e paid:6n emplo4ee has S(000 of sala4 ta> fee. The ne>t S/300 is ta>ed at /0A The ne>t S2=000is ta>ed at 22A 6n4 futhe amount is ta>ed at(0A To the neaest whole pound? which of these isa valid Bounda4 Kalue 6nal4sis test case8A. L#*++B. L!++#C. L!!*+#D. L0+++

Q. &/: 'hich of the following is ;


27/33

6sk: 1'hat ate? $tandad o +heap-da481,9 the custome eplies U+heap-da4J$a4: 1That will #e S//:201 L$$a4: 1That will #e S/C:301 ;D,9L$$a4: 1That will #e SC:31 ;D,9

;ow decide the minimum num#e of tests that ae needed to ensue that all the *uestions have #een asked? all com#inations have occuedand all eplies given.

A. !B. $C. *D.

Q. &&: 'hich of the following should ;


28/33

iii. 6nal4se e*uiements and specifications to detemine test conditions.iv. $pecif4 e>pected esults.6ccoding to the pocess of identif4ing and designing tests? what is the coect ode of these activities8

A. iii, i, iv, ii.

B. iii, iv, i, ii.C. iii, ii, i, iv.D. ii, iii, i, iv.

Q. &C: 'hich is the )


29/33


Q. /: +onside the following statements:i./00A statement coveage guaantees /00A #anch coveage.

ii./00A #anch coveage guaantees /00A statement coveage.iii./00A #anch coveage guaantees /00Adecision coveage.iv./00A decision coveage guaantees /00A #anch coveage. v./00A statement coveage guaantees /00Adecision coveage.A. ii is True1 i, iii, iv < v are &alseB. i < v are True1 ii, iii < iv are &alseC. ii < iii are True1 i, iv < v are &alseD. ii, iii < iv are True1 i < v are &alse

Q. 2: 'hat is the diffeence #etween a po!ect isk and a poduct isk8A. 4roect risks are potential failure areas in the software or s)stem1 product risks are risks that surround the proects capa"ilit) to deliver itso"ectives.B. 4roect risks are the risks that surround the proects capa"ilit) to deliver its o"ectives1

product risks are potential failure areas in the software or s)stem.C. 4roect risks are t)picall) related to supplier issues, organi=ational factors and technicalissues1 product risks are t)picall) related to skill andstaff shortages.D. 4roect risks are risks that delivered software will not work1 product risks are t)picall) related tosupplier issues, organi=ational factors andtechnical issues.

Q. &: Duing which fundamental test pocess activit4 do we detemine if )


30/33

Q. =: ,n a s4stem designed to wok out the ta> to #e paid:6n emplo4ee has S(000 of sala4 ta> fee. The ne>t S/300 is ta>ed at /0A.The ne>t S2=000 afte that is ta>ed at 22A.6n4 futhe amount is ta>ed at (0A.To the neaest whole pound? which of these is a valid Bounda4 Kalue 6nal4sis test case8A. L0+++.

B. L!!*+#.C. L!++#.D. L#*++.

Q. C: 'hich of the following tools is most likel4 to contain a compaato8A. D)namic Anal)sis tool.B. Test 'xecution tool.C. Static Anal)sis tool.D. Securit) tool.

Q./0: 'hen softwae elia#ilit4 measues ae used to detemine when to stop testing? the #est t4pesof test cases to use ae those thatA. 'xercise s)stem functions in proportion to the fre(uenc) the) will "e used in the released productB. 4ush the s)stem "e)ond its designed operation limits and are likel) to make the s)stem failC. 'xercise unusual and o"scure scenarios that ma) not have "een considered in designD. 'xercise the most complicated and the most error%prone portions of the s)stem

//. Load Testing Toolsa reduces the time spent ") the testers" reduces the resources spent hardwarec mostl) used in we" testingd all of the a"ove

/2. Test coveage anal4sis is the pocess of a Creating additional test cases to increase coverage" &inding areas of program exercised ") the test cases

c Determining a (uantitative measure of code coverage, which is adirect measure of (ualit).d All of the a"ove.

/&. +itical in 'e# Testinga 4erformance and &unctionalit)" &unctionalit) and usa"ilit)c 5sa"ilit) and 4erformanced 8one of the a"ove

/(. +lass testinga re(uire a driver to test" no need of instances of other classes

c no need to test the transitionsd all of the a"ove.

/3. Defect Tackinga is the communication channel "etween test team and development team" is the communication channel "etween testing team and the rest of the teamc is the communication channel "etween the testing team and end usersd all of the a"ove


31/33

#7. ssential Testing $kills aea Test 4lanning, 2isk 3anagement, Tool 5sage, Test 'xecution, Defect 3anagement" Test 4lanning, Tool 5sage, Test 'xecution, Defect 3anagement, Test 3easurementc Test 4lanning, Tool 5sage, Test 'xecution, Defect 3anagementd Test 4lanning, Tool 5sage, Test 'xecution, Defect 3anagement, Test Case Design

/. Testing acoss diffeent languages is calleda ?inguistic Testing"?ocali=ation Testingc Both a and "d 8one of the a"ove.

/=.Hieachial $4stema several levels of component that includes o"ects and classes" several levels of component that includes o"ects, classes, s)stemsc several levels of component that includes, foundation component, s)stemsd none of the a"ove.

/C. H4#id Testinga com"ination of one or more testing techni(ues" Com"ination of top%down and "ottom%up testingc Both a and "d 8one of the a"ove.

20. 'hite Bo> Testinga same as glass "ox testing" same as clear "ox testingc "oth a and "d none of the a"ove.

2/. Build Keification Testa same as smoke test" done after each "uild to make sure that the "uild doesnt contain maor errors

c "oth a and "d 8one of the a"ove.

22. +ontent Testinga similar to proof reading" widel) used in we" testingc part of usa"ilit) testingd All of the a"ove.

2&. Decision +oveage.a Testing Boolean expressions which are not in control structures." entire expression is considered as "oolean expression irrespective of logical%and and logical%oroperators

c coverage except switch%statement cases, exception handlersd all of the a"ove.

2(. Banch +oveage @Testing conceptsa another name for decision coverage" another name for all%edges coveragec another name for "asic path coveraged all the a"ove


32/33

23. The following e>ample is aif @condition/ @condition2 VV function/@statement/Felsestatement2F @Testing conceptsa Decision coverage

" Condition coveragec Statement coveraged 4ath Coverage

27.Test cases need to #e witten foa invalid and unexpected conditions" valid and expected conditionsc "oth a and "d none of these

2.Desk +heckinga same as code walkthrough" same as code inspectionc verification of code ") the developersd none of the a"ove.

2=."ath coveage includesa statement coverage" condition coveragec decision coveraged none of these

2C.Tools usagea ver) helpful in regression testing" saves timec helpful in simulating 5sersd all the a"ove

&0. 'hich is a tue pevention mechanisma verif)ing that the executa"le contains a defect" detecting that the executa"le contains a defectc validating that the specified re(uirements are right, complete, achieva"le, reasona"le, testa"le.D verif)ing that the specified re(uirements are right, complete, achieva"le, reasona"le, testa"le

&/. testing aea &ocused Testing, Testing coverage, control flow" Data integrit), 7nternal "oundaries, algorithm specific testingc Both a and "d 'ither a or "

&&. $tuctual Testinga same as "lack "ox testing" same as white "ox testing


33/33

c same as functional testingd none of the a"ove.

&(.+haacteistics of a good testa reasona"le pro"a"ilit) of catching an error and can "e redundant" it is not simple or too complex

c reasona"le pro"a"ilit) of catching an error and cannot "e redundantd it is either too simple or too complex.

&3. 9ind the *uivalence class fo the following test casente a num#e to test the validit4 of #eing accepting the num#es #etween / and CC

a All num"ers M #"

All num"ers N --c 8um"er O +d

All num"ers "etween # and --

&7. 9ind the invalid e*uivalence class fo the following test caseDaw a line up to the length of ( inchesa ?ine with # dot%width" Curvec line with $ inchesd none of the a"ove.

&.Testing use documentation involvesa 7mproved usa"ilit), relia"ilit), maintaina"ilit)" 7nstall%a"ilit), scala"ilit), lia"ilit)c Both a and "d 8one of the a"ove.

&=.$ouces of egession test cases aea "oundar) tests and other preplanned tests." Tests that reveal "ugs in the programc Customer reported "ugs

d All of the a"ove

&C.,dentif4 which one is an intenal failuea Dela)ing testers access to areas of the code" 2eplacement with updated productc Training programmers to make or miss fewer "ugsd Testing ") Tech. Support

(0.,dentif4 which one is a load conditiona ?ost messages" Task starts "efore its prere(uisites are met.c ?ost or out of s)nc messagesd 'arl) end of string

6nswes:@.#%D @.%B @.!%B @.$%B @.*%B @.%A @.%D @.0%B @.-%B @.#+%A @.##%D @.#%A @.#!%C @.#$%A @.#*%D @.#%C @.#%B @.#0%D @.#-%B @.+%C @.#%C @.%D @.!%B @.$%D @.*%A @.%C @.%C @.0%C @.-%D@.!+%D @.!#%A @.!%C @.!!%B @.!$%C @.!*%D @.!%B @.!%C @.!0%D @.!-%A @.$+%A

istqb foundation sample question paper no 22 to 27

Documents