Final Exam (QH BST)

8/11/2019 Final Exam (QH BST)

http://slidepdf.com/reader/full/final-exam-qh-bst 1/7

Basics of Software Testingbased on the ISTQB-Certified Tester

Foundation Level Curriculum

Final Exam

Time Allowed: 1 1/4 hour (75 min)

Number of Questions: 40

You are not allowed to make copies or use an part of this e!am unless ou have e!plicit approval b an

authori"ed Qualit #ouse representative$ Should ou have %uestions or want to make a re%uest& please

contact trainin'(%ualithouse$bi"

mailto:[email protected]

mailto:[email protected]



)*+,./0/ 12 Qualit #ouse 3 Ос!"# $ %&с%"$&%! ' ##%4,5/612 4+78129 :; ,/40/7.+< :==> ?$

Answer *heet+nstru,tions:

@ark our answers with a solid dot or - mark$

Ase black pencil$ ttempt .ll 40 %uestions

@ark onl one .nswer per %uestion rase an answer ou decide to chan'e and mark our new chosen answer clearl$

Q1 a b c d e

Q a b c d e

Q a b c d e

Q4 a b c d e

Q5 a b c d e

Q a b c d e

Q7 a b c d e

Q2 a b c d e

Q3 a b c d e

Q10 a b c d e

Q11 a b c d e

Q1 a b c d e

Q1 a b c d e

Q14 a b c d e

Q15 a b c d e

Q1 a b c d e

Q17 a b c d e

Q12 a b c d e

Q13 a b c d e

Q0 a b c d e

Your Dame9

----------------------------------------------

Q1 a b c d e

Q a b c d e

Q a b c d e

Q4 a b c d e

Q5 a b c d e

Q a b c d e

Q7 a b c d e

Q2 a b c d e

Q3 a b c d e

Q0 a b c d e

Q1 a b c d e

Q a b c d e

Q a b c d e

Q4 a b c d e

Q5 a b c d e

Q a b c d e

Q7 a b c d e

Q2 a b c d e

Q3 a b c d e

Q40 a b c d e

Copri'ht E :==-:==> Qualit #ouse& www$%ualithouse$bi" ,0+$ 0 G



Questionsnswer all %uestions$ Ase the answer sheet$

Q1 hen . dei.tion from the s6e,ified ore6e,ted beh.iour is isible to end'users8

this is ,.lledaH an error

bH a fault

cH a failure

dH a defect

eH a mistake

Q 9eression testin should be 6erformedi ever weekii after the software has chan'ediii as often as possibleiv when the environment has chan'edv when the proect mana'er sas

aH i J ii are true& iii K v are false

bH ii& iii J iv are true& v J v are false

cH ii J iv are true& i& iii J v are false

dH ii is true& v& iii& iv and v are false

eH ll of the above are true

Q +;;; 23 test 6l.n do,ument.tion st.nd.rd,ont.ins .ll of the followin e,e6taH test items

bH test deliverables

cH test tasks

dH test environmenteH test specification

Q4 Testin should be sto66ed whenaH all the planned tests have been run

bH time has run out

cH all faults have been fi!ed correctl

dH both aH and cH

eH it depends on the risks for the sstem bein'tested

Q5 <rder numbers on . sto,= ,ontrol s>stem ,.nr.ne between 10 000 .nd 33 333 in,lusie?

hi,h of the followin in6uts miht be .result of desinin tests for onl> [email protected],e ,l.sses .nd .lid bound.riesaH === 3 >= === 3 MM MMM

bH M MMM 3 >= === 3 == ===

cH = === 3 >= === 3 MM MMM

dH = === 3 MM MMM

eH M MMM 3 = === 3 >= === 3 MM MMM 3 == ===

Q Bonsider the followin st.tements .boute.rl> test desin:i earl test desi'n can prevent fault

multiplication

ii faults found durin' earl test desi'nare more e!pensive to fi!

iii earl test desi'n can find faultsiv earl test desi'n can cause chan'es

to the re%uirementsv earl test desi'n takes more effort

aH i& iii J iv are true$ ii J v are false

bH iii is true& i& ii& iv& J v are false

cH iii J iv are true$ i& ii J v are false

dH i& iii& iv J v are true& ii is false

eH i J iii are true& ii& iv J v are false

Q7 Non'fun,tion.l s>stem testin in,ludes:aH testin' to see where the sstem does not

function correctl

bH testin' %ualit attributes of the sstemincludin' performance and usabilit

cH 'ainin' user approval for the sstem

dH testin' a sstem feature usin' onl thesoftware re%uired for that function

eH testin' for functions that should not e!ist

Q2 hi,h of the followin is N<T 6.rt of,onfiur.tion m.n.ementaH status accountin' of confi'uration items

bH auditin' conformance to ISN M===

cH identification of test versions

dH record of chan'es to documentation overtime

eH controlled access to the libraries of items

Q3 hi,h of the followin is the m.in 6ur6ose of the inter.tion str.te> for inter.tiontestin in the sm.llaH to ensure that all of the small modules are

tested ade%uatel

bH to ensure that the sstem interfaces to othersstems and networks

cH to specif which modules to combine when&and how man at once

dH to ensure that the inte'ration testin' can beperformed b a small team

eH to specif how the software should bedivided into modules

Q10 h.t is the 6ur6ose of test ,om6letion,riteri. in . test 6l.naH to know when a specific test has finished its

e!ecution

bH to ensure that the test case specification iscomplete

cH to set the criteria used in 'eneratin' testinputs

dH to know when test plannin' is complete

eH to plan when to stop testin'

Q11 Bonsider the followin st.tements

i an incident ma be closed withoutbein' fi!ed$ii incidents ma not be raised a'ainst

documentation$



iii the final sta'e of incident trackin' isfi!in'$

iv the incident record does not includeinformation on test environments$

v incidents should be raised whensomeone other than the author ofthe software performs the test$

aH ii and v are true& i& iii and iv are false

bH i and v are true& ii& iii and iv are falsecH i& iv and v are true& ii and iii are false

dH i and ii are true& iii& iv and v are false

eH i is true& ii& iii& iv and v are false

Q1 Cien the followin ,ode8 whi,h is true .boutthe minimum number of test ,.ses re@uiredfor full st.tement .nd br.n,h ,oer.e

Oead POead QIF PQ R == T#D

Print Lar'eDIF

IF P R >= T#DPrint P Lar'eDIF

aH test for statement covera'e& ; for branchcovera'e

bH test for statement covera'e& : for branchcovera'e

cH test for statement covera'e& for branchcovera'e

dH : tests for statement covera'e& ; for branchcovera'e

eH : tests for statement covera'e& : for branchcovera'e

Q1 Bonsider the followin st.tements:i ==U statement covera'e

'uarantees ==U branch covera'e$ii ==U branch covera'e 'uarantees

==U statement covera'e$iii ==U branch covera'e 'uarantees

==U decision covera'e$iv ==U decision covera'e 'uarantees

==U branch covera'e$v ==U statement covera'e

'uarantees ==U decisioncovera'e$

aH ii is True& i& iii& iv J v are False

bH i is True& ii& iii& iv J v are FalsecH i J v are True& ii& iii J iv are False

dH ii J iii are True& i& iv J v are False

eH ii& iii J iv are True& i J v are False

Q14 Dun,tion.l s>stem testin isaH testin' that the sstem functions with other

sstems

bH testin' b users to check that the sstem willperform business functions

cH testin' that the components that comprisethe sstem function to'ether

dH testin' the end to end functionalit of thesstem as a whole

eH testin' the sstem performs functions withinspecified response times

Q15 +n,idents would not be r.ised ..instaH re%uirements

bH documentation

cH on-line help

dH test cases

eH improvements su''ested b users

Q1 hi,h of the followin items would not ,omeunder Bonfiur.tion E.n.ementaH software

bH operatin' sstems

cH test documentation

dH live data

eH user re%uirement documents

Q17 E.inten.n,e testin isaH updatin' the tests when the software has

chan'ed

bH testin' ver old sstems

cH testin' a sstem that has been chan'ed

dH testin' b users to ensure that the sstemmeets a business need

eH testin' to maintain business advanta'e

Q12 h.t ,.n st.ti, .n.l>sis N<T findaH the use of a variable before it has been

defined

bH unreachable VWdeadXH code

cH whether the value stored in a variable iscorrect

dH the re-definition of a variable before it has

been usedeH arra bound violations

Q13 hi,h of the followin te,hni@ues is N<T .bl.,= bo te,hni@ueaH e%uivalence partitionin'

bH state transition testin'

cH LCS

dH snta! testin'

eH boundar value analsis

Q0 Fet. testin is:aH performed b customers at their own site

bH performed b customers at the softwaredeveloperZs site

cH performed b an Independent Test Team

dH useful to test bespoke software

eH performed as earl as possible in the lifeccle

Q1 Cien the followin t>6es of tool8 whi,h toolswould t>6i,.ll> be used b> deelo6ers8 .ndwhi,h b> .n inde6endent s>stem test te.m

i static analsisii performance testin'

iii test mana'ementiv dnamic analsisv test runnin'vi test data preparation



aH developers would tpicall use i& iv and vi[test team ii& iii and v

bH developers would tpicall use i and iv& testteam ii& iii& v and vi

cH developers would tpicall use i& ii& iii and iv[test team v and vi

dH developers would tpicall use ii& iv and vi[test team i& iii and v

eH developers would tpicall use i& iii& iv and v[test team ii and vi

Q The m.in fo,us of .,,e6t.n,e testin isaH findin' faults in the sstem

bH ensurin' that the sstem is acceptable to allusers

cH testin' the sstem with other sstems

dH testin' from a business perspective

eH testin' b an independent test team

Q hi,h of the followin st.tements .bout the,om6onent testin st.nd.rd is DAG*;aH black bo! desi'n techni%ues all have an

associated measurement techni%ue$

bH white bo! desi'n techni%ues all have anassociated measurement techni%ue$

cH cclomatic comple!it is not a testmeasurement techni%ue

dH black bo! measurement techni%ues all havean associated test desi'n techni%ue$

eH white bo! measurement techni%ues all havean associated test desi'n techni%ue$

Q4 hi,h of the followin st.tements is N<TtrueaH inspection is the most formal review process

bH inspections should be led b a trained leader

cH mana'ers can perform inspections onmana'ement documents

dH inspection is appropriate even when thereare no written documents

eH inspection compares documents withpredecessor VsourceH documents

Q5 A t>6i,.l ,ommer,i.l test ee,ution toolwould be .ble to 6erform .ll of the followin8

;-B;HT:aH 'eneratin' e!pected outputs

bH replain' inputs accordin' to a pro'rammedscript

cH comparison of e!pected outcomes with actualoutcomes

dH recordin' test inputs

eH readin' test values from a data file

Q The differen,e between re'testin .ndreression testin is:aH re-testin' is runnin' a test a'ain[ re'ression

testin' looks for une!pected side-effects

bH re-testin' looks for une!pected side-effects[re'ression testin' is repeatin' those tests

cH re-testin' is done after faults are fi!ed[re'ression testin' is done earlier

dH re-testin' uses different environments&re'ression testin' uses the sameenvironment

eH re-testin' is done b developers& re'ressiontestin' is done b independent testers

Q7 ;6e,ted results .re:aH onl important in sstem testin'

bH onl used in component testin'

cH never specified in advance

dH most useful when specified in advance

eH derived from the code

Q2 h.t t>6e of reiew re@uires form.l entr>.nd eit ,riteri.8 in,ludin metri,s:aH informal review

bH walkthrou'h

cH inspectiondH mana'ement review

eH post proect review

Q3 +n whi,h of the followin does +m6.,tAn.l>sis h.e the hihest .lue .ndim6ort.n,eaH component testin'

bH inte'ration testin' in the small

cH non-functional sstem testin'

dH user acceptance testin'

eH maintenance testin'

Q0 h.t is N<T in,luded in t>6i,.l ,osts for .nins6e,tion 6ro,essaH trainin' in the inspection process

bH settin' up forms and databases

cH analsin' metrics and improvin' processes

dH writin' the documents to be inspected

eH time spent on the document outside themeetin'

Q1 hi,h of the followin is N<T . .lid testobIe,tie:

aH to show that the software meets itsre%uirement

bH to find faults in the software

cH to prove that the software has no faults

dH to 'ive confidence in the software

eH to find performance problems

Q hi,h e6ression best m.t,hes the followin,h.r.,teristi,s .nd reiew 6ro,esses:

led b the author: undocumented; no mana'ement participation led b a trained moderator or leader

> uses entr and e!it criteria

s inspectiont peer review



u informal reviewv walkthrou'h

aH s \ & t \ ;& u \ : and >& v \

bH s \ and >& t \ ;& u \ :& v \

cH s \ and >& t \ ;& u \ :& v \

dH s \ >& t \ & u \ ;& v \ and :

eH s \ and >& t \ & u\ :& v \ ;

Q hi,h of the followin is N<T 6.rt of s>stemtestinaH business process-based testin'

bH performance& load and stress testin'

cH re%uirements-based testin'

dH usabilit testin'

eH top-down inte'ration testin'

Q4 hi,h st.tement .bout e6e,ted out,omes isDAG*;aH e!pected outcomes are defined b the

softwareZs behaviour

bH e!pected outcomes are derived from aspecification& not from the code

cH e!pected outcomes include outputs to ascreen and chan'es to files and databases

dH e!pected outcomes should be predictedbefore a test is run

eH e!pected outcomes ma include timin'constraints such as response times

Q5 hi,h of the followin h.s the re.testinfluen,e on the m.int.in.bilit> of . s>stemaH @odularit

bH @emor in use

cH Oesponse time

dH Oobustness

eH ase of learnin'

Q The ,ost of fiin . f.ult:aH is not important

bH increases as we move the product towardslive use

cH decreases as we move the product towardslive use

dH is more e!pensive if found in re%uirementsthan functional desi'n

eH can never be determined

Q7 hi,h of the followin is N<T in,luded in theTest Hl.n do,ument of the TestJo,ument.tion *t.nd.rdaH Test items Vi$e$ software versionsH

bH ]hat is not to be tested

cH Test environments

dH Qualit plans

eH Schedules and deadlines

Q2 Bould reiews or ins6e,tions be ,onsidered6.rt of testinaH no& because the appl to development

documentation

bH no& because the are normall applied beforetestin'

cH no& because the do not appl to the testdocumentation

dH es& because both help detect faults andimprove %ualit

eH es& because testin' includes all non-constructive activities

Q3 hi,h of the followin is not 6.rt of6erform.n,e testinaH measurin' response times

bH measurin' transaction rates

cH recover testin'

dH simulatin' man users

eH 'eneratin' man transactions

Q40 ;rror uessin is best usedaH as the first approach to derivin' test cases

bH after more formal techni%ues have beenapplied

cH b ine!perienced testers

dH after the sstem has 'one live

eH onl b end-users



C

C

E

E

C

A

B

B

C

E

B

B

E

D

E

D

C

C

C

A

B

D

A

D

A

A

D

C

E

D

C

B

E

A

B

A

D

D

C

B

Final Exam (QH BST)

Documents

Transcript of Final Exam (QH BST)