1.

Software testing activities should start

a. as soon as the code is written
b. during the design stage
c. when the requirements have been formally documented
d. as soon as possible in the development life cycle
2.Faults found by users are due to:
a. Poor quality software
b. Poor software and poor testing
c. bad luck
d. insucient time for testing
3.What is the main reason for testing software before releasing it?
a. to show that system will work after release
b. to decide when the software is of sufcient quality to release
c. to fnd as many bugs as possible before release
d. to give information for a risk based decision about release
!. which of the following statements is not true
a. performance testing can be done during unit testing as well as during the testing
of whole system
b. "he acceptance test does not necessarily include a regression test
c. #eri$cation activities should not involve testers %reviews& inspections etc'
d. "est environments should be as similar to production environments as possible
(. )hen reporting faults found to developers& testers should be:
a. as polite& constructive and helpful as possible
b. $rm about insisting that a bug is not a *feature+ if it should be $,ed
c. diplomatic& sensitive to the way they may react to criticism
d. -ll of the above
../n which order should tests be run0
a. the most important tests $rst
b. the most dicult tests $rst%to allow ma,imum time for $,ing'
c. the easiest tests $rst%to give initial con$dence'
d. the order they are thought of
1. "he later in the development life cycle a fault is discovered& the more e,pensive
it is to $,. why0
a. the documentation is poor& so it takes longer to $nd out what the software is
doing.
b. wages are rising
c. the fault has been built into more documentation&code&tests& etc
d. none of the above
2. )hich is not true3"he black bo, tester
a. should be able to understand a functional speci$cation or requirements document
b. should be able to understand the source code.
c. is highly motivated to $nd faults
d. is creative to $nd the system4s weaknesses
5. - test design technique is
a. a process for selecting test cases
b. a process for determining e,pected outputs
c. a way to measure the quality of software
d. a way to measure in a test plan what has to be done
16. "estware%test cases& test dataset'
a. needs con$guration management 7ust like requirements& design and code
b. should be newly constructed for each new version of the software
c. is needed only until the software is released into production or use
d. does not need to be documented and commented& as it does not form part of the
released software system
11. -n incident logging system
a only records defects
b is of limited value
c is a valuable source of pro7ect information during testing if it contains all incidents
d. should be used only by the test team.
1. !ncreasing the quality of the software" by better development
methods" will a#ect the time needed for testing $the test phases% by&
a. reducing test time
b. no change
c. increasing test time
d. can't say
18. 9overage measurement
a. is nothing to do with testing
b. is a partial measure of test thoroughness
c. branch coverage should be mandatory for all software
d. can only be applied at unit or module testing& not at system testing
1(. When should you stop testing?
a. when time for testing has run out.
b. when all planned tests have been run
c. when the test completion criteria have been met
d. when no faults have been found by the tests run
1(. )hich of the following is true0
a. 9omponent testing should be black bo,& system testing should be white bo,.
b. if u $nd a lot of bugs in testing& you should not be very con$dent about the
quality of software
c. the fewer bugs you $nd&the better your testing was
d. the more tests you run& the more bugs you will $nd.
1). What is the important criterion in deciding what testing technique to
use?
a. how well you know a particular technique
b. the ob*ective of the test
c. how appropriate the technique is for testing the application
d. whether there is a tool to support the technique
11. /f the pseudocode below were a programming language &how many tests are
required to achieve 166: statement coverage0
/f ,;8 then
<isplay=message>?
/f y;2 then
<isplay=message@?
Alse
<isplay=messageB?
Alse
<isplay=messageB?
a. 1
b. 2
c. 8
d. !
1+. ,sing the same code e-ample as question 1."how many tests are
required to achieve 1//0 branch1decision coverage?
a. 1
b.
c. 3
d. (
15 )hich of the following is CD" a type of non3functional test0
a. State3"ransition
b. Esability
c. Performance
d. Security
26. )hich of the following tools would you use to detect a memory leak0
a. State analysis
b. 9overage analysis
c. <ynamic analysis
d. Femory analysis
21. )hich of the following is CD" a standard related to testing0
a. /AAA225
b. /AAA.16
c. GS152(31
d. GS152(32
22.which of the following is the component test standard0
a. /AAA 225
b. /AAA .16
c. GS152(31
d. GS152(32
28 which of the following statements are true0
a. Faults in program speci$cations are the most e,pensive to $,.
b. Faults in code are the most e,pensive to $,.
c. Faults in requirements are the most e,pensive to $,
d. Faults in designs are the most e,pensive to $,.
2!. )hich of the following is not the integration strategy0
a. <esign based
b. Gig3bang
c. Gottom3up
d. "op3down
2(. )hich of the following is a black bo, design technique0
a. statement testing
b. equivalence partitioning
c. error3 guessing
d. usability testing
2.. - program with high cyclometic comple,ity is almost likely to be:
a. Harge
b. Small
c. <icult to write
d. <icult to test
21. )hich of the following is a static test0
a. code inspection
b. coverage analysis
c. usability assessment
d. installation test
22. )hich of the following is the odd one out0
a. white bo,
b. glass bo,
c. structural
d. functional
25. - program validates a numeric $eld as follows:
values less than 16 are re7ected& values between 16 and 21 are accepted& values
greater than or equal to 22 are re7ected
which of the following input values cover all of the equivalence partitions0IIIIII
IIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIIII
II
-CS)AJS:
1.d
2.b
8.d
!.c
(.d
..a
1.c
2.b
5.a
16.a
11.c
12.a
18.b
1!.c
1(.b
1..b
11.c
12.c
15.a
26.c
21.b
22.d
28.c
2!.a
2(.b
2..d
21.a
22.d
25.c
86.b
1 )e split testing into distinct stages primarily because:
a'Aach test stage has a diKerent purpose.
b'/t is easier to manage testing in stages.
c')e can run diKerent tests in diKerent environments.
d'"he more stages we have& the better the testing.
2 )hich of the following is likely to bene$t most from the use of test tools providing
test capture and replay facilities0
a'Jegression testing
b'/ntegration testing
c'System testing
d'Eser acceptance testing
8 )hich of the following statements is CD" correct0
a'- minimal test set that achieves 166: H9S-L coverage will also achieve 166:
branch coverage.
b'- minimal test set that achieves 166: path coverage will also achieve 166:
statement coverage.
c'- minimal test set that achieves 166: path coverage will generally detect more
faults than one that achieves 166: statement coverage.
d'- minimal test set that achieves 166: statement coverage will generally detect
more faults than one that achieves 166: branch coverage.
( Which of the following requirements is testable?
a%2he system shall be user friendly.
b%2he safety3critical parts of the system shall contain / faults.
c%2he response time shall be less than one second for the specifed design
load.
d%2he system shall be built to be portable.
( -nalyse the following highly simpli$ed procedure:
-sk: *)hat type of ticket do you require& single or return0+
/F the customer wants Mreturn4
-sk: *)hat rate& Standard or 9heap3day0+
/F the customer replies M9heap3day4
Say: *"hat will be N11:26+
AHSA
Say: *"hat will be N15:(6+
AC</F
AHSA
Say: *"hat will be N5:1(+
AC</F
Cow decide the minimum number of tests that are needed to ensure that all
the questions have been asked& all combinations have occurred and all
replies given.
a'8
b'!
c'(
d'.
. Arror guessing:
a'supplements formal test design techniques.
b'can only be used in component& integration and system testing.
c'is only performed in user acceptance testing.
d'is not repeatable and should not be used.
1 )hich of the following is CD" true of test coverage criteria0
a'"est coverage criteria can be measured in terms of items e,ercised by a test suite.
b'- measure of test coverage criteria is the percentage of user requirements
covered.
c'- measure of test coverage criteria is the percentage of faults found.
d'"est coverage criteria are often used when specifying test completion criteria.
2 /n prioritising what to test& the most important ob7ective is to:
a'$nd as many faults as possible.
b'test high risk areas.
c'obtain good test coverage.
d'test whatever is easiest to test.
5 Oiven the following sets of test management terms %v3P'& and activity descriptions
%134%" which one of the following best pairs the two sets?
v 5 test control
w 5 test monitoring
- 3 test estimation
y 3 incident management
6 3 confguration control
1 3 calculation of required test resources
3 maintenance of record of test results
3 3 re3allocation of resources when tests overrun
( 3 report on deviation from test plan
4 3 tracking of anomalous test results
a%v33"w3"-31"y34"63(
b%v3"w34"-31"y3("633
c%v33"w3("-31"y34"63
d%v3"w31"-3("y33"634
16 )hich one of the following statements about system testing is CD" true0
a'System tests are often performed by independent teams.
b'Functional testing is used more than structural testing.
c'Faults found during system tests can be very e,pensive to $,.
d'And3users should be involved in system tests.
11 )hich of the following is false0
a'/ncidents should always be $,ed.
b'-n incident occurs when e,pected and actual results diKer.
c'/ncidents can be analysed to assist in test process improvement.
d'-n incident can be raised against documentation.
1 7nough testing has been performed when&
a%time runs out.
b%the required level of confdence has been achieved.
c%no more faults are found.
d%the users won't fnd any serious faults.
18 )hich of the following is CD" true of incidents0
a'/ncident resolution is the responsibility of the author of the software under test.
b'/ncidents may be raised against user requirements.
c'/ncidents require investigation andQor correction.
d'/ncidents are raised when e,pected and actual results diKer.
1! )hich of the following is not described in a unit test standard0
a'synta, testing
b'equivalence partitioning
c'stress testing
d'modi$ed conditionQdecision coverage
1( )hich of the following is false0
a'/n a system two diKerent failures may have diKerent severities.
b'- system is necessarily more reliable after debugging for the removal of a fault.
c'- fault need not aKect the reliability of a system.
d'Endetected errors may lead to faults and eventually to incorrect behaviour.
1. )hich one of the following statements& about capture3replay tools& is CD"
correct0
a'"hey are used to support multi3user testing.
b'"hey are used to capture and animate user requirements.
c'"hey are the most frequently purchased types of 9-S" tool.
d' "hey capture aspects of user behaviour.
1. 8ow would you estimate the amount of re3testing likely to be required?
a%9etrics from previous similar pro*ects
b%:iscussions with the development team
c%2ime allocated for regression testing
d%a ; b
12 )hich of the following is true of the #3model0
a'/t states that modules are tested against user requirements.
b'/t only models the testing phase.
c'/t speci$es the test techniques to be used.
d'/t includes the veri$cation of designs.
1< 2he oracle assumption&
a%is that there is some e-isting system against which test output may be
checked.
b%is that the tester can routinely identify the correct outcome of a test.
c%is that the tester knows everything about the software under test.
d%is that the tests are reviewed by e-perienced testers.
26 )hich of the following characterises the cost of faults0
a'"hey are cheapest to $nd in the early development phases and the most
e,pensive to $, in the latest test phases.
b'"hey are easiest to $nd during system testing but the most e,pensive to $, then.
c'Faults are cheapest to $nd in the early development phases but the most
e,pensive to $, then.
d'-lthough faults are most e,pensive to $nd during early development phases& they
are cheapest to $, then.
21 )hich of the following should CD" normally be an ob7ective for a test0
a'"o $nd faults in the software.
b'"o assess whether the software is ready for release.
c'"o demonstrate that the software doesn4t work.
d'"o prove that the software is correct.
22 )hich of the following is a form of functional testing0
a'Goundary value analysis
b'Esability testing
c'Performance testing
d'Security testing
28 )hich of the following would CD" normally form part of a test plan0
a'Features to be tested
b'/ncident reports
c'Jisks
d'Schedule
2! )hich of these activities provides the biggest potential cost saving from the use
of 9-S"0
a'"est management
b'"est design
c'"est e,ecution
d'"est planning
2( )hich of the following is CD" a white bo, technique0
a'Statement testing
b'Path testing
c'<ata Row testing
d'State transition testing
2. <ata Row analysis studies:
a'possible communications bottlenecks in a program.
b'the rate of change of data values as a program e,ecutes.
c'the use of data on paths through the code.
d'the intrinsic comple,ity of the code.
21 /n a system designed to work out the ta, to be paid:
-n employee has N!666 of salary ta, free. "he ne,t N1(66 is ta,ed at 16:
"he ne,t N22666 is ta,ed at 22:
-ny further amount is ta,ed at !6:
"o the nearest whole pound& which of these is a valid Goundary #alue -nalysis test
case0
a'N1(66
b'N82661
c'N88(61
d'N22666
22 -n important bene$t of code inspections is that they:
a'enable the code to be tested before the e,ecution environment is ready.
b'can be performed by the person who wrote the code.
c'can be performed by ine,perienced staK.
d'are cheap to perform.
25 )hich of the following is the best source of A,pected Dutcomes for Eser
-cceptance "est scripts0
a'-ctual results
b'Program speci$cation
c'Eser requirements
d'System speci$cation
86 )hat is the main diKerence between a walkthrough and an inspection0
a'-n inspection is lead by the author& whilst a walkthrough is lead by a trained
moderator.
b'-n inspection has a trained leader& whilst a walkthrough has no leader.
c'-uthors are not present during inspections& whilst they are during walkthroughs.
d' - walkthrough is lead by the author& whilst an inspection is lead by a trained
moderator.
81 )hich one of the following describes the ma7or bene$t of veri$cation early in the
life cycle0
a'/t allows the identi$cation of changes in user requirements.
b'/t facilitates timely set up of the test environment.
c'/t reduces defect multiplication.
d'/t allows testers to become involved early in the pro7ect.
82 /ntegration testing in the small:
a'tests the individual components that have been developed.
b'tests interactions between modules or subsystems.
c'only uses components that form part of the live system.
d'tests interfaces to other systems.
88 Static analysis is best described as:
a'the analysis of batch programs.
b'the reviewing of test plans.
c'the analysis of program code.
d'the use of black bo, testing.
8! -lpha testing is:
a'post3release testing by end user representatives at the developer4s site.
b'the $rst testing that is performed.
c'pre3release testing by end user representatives at the developer4s site.
d'pre3release testing by end user representatives at their sites.
8( - failure is:
a'found in the software? the result of an error.
b'departure from speci$ed behaviour.
c'an incorrect step& process or data de$nition in a computer program.
d'a human action that produces an incorrect result.
8. /n a system designed to work out the ta, to be paid:
-n employee has N!666 of salary ta, free. "he ne,t N1(66 is ta,ed at 16:
"he ne,t N22666 is ta,ed at 22:
-ny further amount is ta,ed at !6:
)hich of these groups of numbers would fall into the same equivalence class0
a'N!266? N1!666? N22666
b'N(266? N((66? N22666
c'N22661? N82666? N8(666
d'N(266? N22666? N82666
81 "he most important thing about early test design is that it:
a'makes test preparation easier.
b'means inspections are not required.
c'can prevent fault multiplication.
d'will $nd all faults.
82 )hich of the following statements about reviews is true0
a'Jeviews cannot be performed on user requirements speci$cations.
b'Jeviews are the least eKective way of testing code.
c'Jeviews are unlikely to $nd faults in test plans.
d'Jeviews should be performed on speci$cations& code& and test plans.
85 "est cases are designed during:
a'test recording.
b'test planning.
c'test con$guration.
d'test speci$cation.
!6 - con$guration management system would CD" normally provide:
a'linkage of customer requirements to version numbers.
b'facilities to compare test results with e,pected results.
c'the precise diKerences in versions of software component source code.
d'restricted access to the source code library.
-
2-
8<
!9
(-
.-
19
2G
59
16<
11-
12G
18-
1!9
1(G
1.G
11<
12<
15G
26-
21<
22-
28G
2!9
2(<
2.9
219
22-
259
86<
819
82G
889
8!9
8(G
8.<
819
82<
85<
!6G
S1- deviation from the speci$ed or e,pected behavior that is visible to end3users is
called:
a'an error
b'a fault
c'a failure
d'a defect
S2Jegression testing should be performed:
v'every week
w'after the software has changed
,'as often as possible
y'when the environment has changed
P'when the pro7ect manager says
a'v T w are true& ,& y T P are false
b'w& , T y are true& v T P are false
c'w T y are true& v& , T P are false
d'w is true& v& ,& y T P are false
S8/AAA 225 test plan documentation standard contains all of the following e,cept
a'test items
b'test deliverables
c'test tasks
d'test speci$cations
S!)hen should testing be stopped0
a'when all the planned tests have been run
b'when time has run out
c'when all faults have been $,ed correctly
d'it depends on the risks for the system being tested
S(Drder numbers on a stock control system can range between 16666 and 55555
inclusive. )hich of the following inputs might be a result of designing tests for only
valid equivalence classes and valid boundaries0
a'1666& (6666& 55555
b'5555& (6666& 166666
c'16666& (6666& 55555
d'16666& 55555& 166666
S.9onsider the following statements about early test design:
i.early test design can prevent fault multiplication
ii.faults found during early test design are more e,pensive to $,
iii.early test design can $nd faults
iv.early test design can cause changes to the requirements
v.early test design normally takes more eKort
a'i& iii T iv are true? ii T v are false
b'iii T iv are true? i& ii T v are false
c'i& iii& iv T v are true? ii is false
d'i T ii are true? iii& iv T v are false
S1Con3functional system testing includes:
a'testing to see where the system does not function correctly
b'testing quality attributes of the system including performance and usability
c'testing a system function using only the software required for that function
d'testing for functions that should not e,ist
=+Which of the following is >?2 part of confguration management?
a%auditing conformance to !@? <///
b%status accounting of confguration items
c%identifcation of test versions
d%controlled library access
S5)hich of the following is the main purpose of the integration strategy for
integration testing in the small0
a'to ensure that all of the small modules are tested adequately
b'to ensure that the system interfaces to other systems and networks
c'to specify which modules to combine when& and how many at once
d'to specify how the software should be divided into modules
S16)hat is the purpose of a test completion criterion0
a'to know when a speci$c test has $nished its e,ecution
b'to ensure that the test case speci$cation is complete
c'to set the criteria used in generating test inputs
d'to determine when to stop testing
S119onsider the following statements:
i.an incident may be closed without being $,ed.
ii.incidents may not be raised against documentation.
iii.the $nal stage of incident tracking is $,ing.
iv.the incident record does not include information on test environments.
a'ii is true& i& iii and iv are false
b'i is true& ii& iii and iv are false
c'i and iv are true& ii and iii are false
d'i and ii are true& iii and iv are false
=1Aiven the following code" which statement is true about the minimum
number of test cases required for full statement and branch coverage?
Bead p
Bead q
!C pDq E 1// 287>
Frint GHargeG
7>: !C
!C p E 4/ 287>
Frint Gp HargeG
7>: !C
a%1 test for statement coverage" 3 for branch coverage
b%1 test for statement coverage" for branch coverage
c%1 test for statement coverage" 1 for branch coverage
d% tests for statement coverage" for branch coverage
S189onsider the following statements:
i.166: statement coverage guarantees 166: branch coverage.
ii166: branch coverage guarantees 166: statement coverage.
iii.166: branch coverage guarantees 166: decision coverage.
iv.166: decision coverage guarantees 166: branch coverage.
v.166: statement coverage guarantees 166: decision coverage.
a'ii is "rue? i& iii& iv T v are False
b'i T v are "rue? ii& iii T iv are False
c'ii T iii are "rue? i& iv T v are False
d'ii& iii T iv are "rue? i T v are False
S1!Functional system testing is:
a'testing that the system functions with other systems
b'testing that the components that comprise the system function together
c'testing the end to end functionality of the system as a whole
d'testing the system performs functions within speci$ed response times
=14!ncidents would not be raised against&
a%requirements
b%documentation
c%test cases
d%improvements suggested by users
=1)Which of the following items would not come under Ionfguration
9anagement?
a%operating systems
b%test documentation
c%live data
d%user requirement documents
S11Faintenance testing is:
a'updating tests when the software has changed
b'testing a released system that has been changed
c'testing by users to ensure that the system meets a business need
d'testing to maintain business advantage
S12)hat can static analysis CD" $nd0
a'the use of a variable before it has been de$ned
b'unreachable %*dead+' code
c'memory leaks
d'array bound violations
S15)hich of the following techniques is CD" a black bo, technique0
a'state transition testing
b'H9S-L
c'synta, testing
d'boundary value analysis
S26Geta testing is:
a'performed by customers at their own site
b'performed by customers at the software developerUs site
c'performed by an /ndependent "est "eam
d'performed as early as possible in the life cycle
=1Aiven the following types of tool" which tools would typically be used
by developers" and which by an independent system test team?
i.static analysis
ii performance testing
iii.test management
iv.dynamic analysis
a%developers would typically use i and ivJ test team ii and iii
b%developers would typically use i and iiiJ test team ii and iv
c%developers would typically use ii and ivJ test team i and iii
d%developers would typically use i" iii and ivJ test team ii
S22"he main focus of acceptance testing is:
a'$nding faults in the system
b'ensuring that the system is acceptable to all users
c'testing the system with other systems
d'testing from a business perspective
=3Which of the following statements about component testing is CKH@7?
a%black bo- test design techniques all have an associated test
measurement technique
b%white bo- test design techniques all have an associated test
measurement technique
c%cyclomatic comple-ity is not a test measurement technique
d%black bo- test measurement techniques all have an associated test
design technique
S2!)hich of the following statements is CD" true0
a'inspection is the most formal review process
b'inspections should be led by a trained leader
c'managers can perform inspections on management documents
d'inspection is appropriate even when there are no written documents
S2(- typical commercial test e,ecution tool would be able to perform all of the
following& A>9AP":
a'calculating e,pected outputs
b'comparison of e,pected outcomes with actual outcomes
c'recording test inputs
d'reading test values from a data $le
S2. "he diKerence between re3testing and regression testing is:
a're3testing ensures the original fault has been removed? regression testing looks
for une,pected side3eKects
b're3testing looks for une,pected side3eKects? regression testing ensures the
original fault has been removed
c're3testing is done after faults are $,ed? regression testing is done earlier
d're3testing is done by developers? regression testing is done by independent
testers
S21 A,pected results are:
a'only important in system testing
b'only used in component testing
c'most useful when speci$ed in advance
d'derived from the code
S22 )hat type of review requires formal entry and e,it criteria& including metrics:
a'walk through
b'inspection
c'management review
d'post pro7ect review
S25 )hich of the following uses /mpact -nalysis most0
a'component testing
b'non3functional system testing
c'user acceptance testing
d'maintenance testing
S86 )hat is CD" included in typical costs for an inspection process0
a'setting up forms and databases
b'analyPing metrics and improving processes
c'writing the documents to be inspected
d'time spent on the document outside the meeting
S81 )hich of the following is CD" a reasonable test ob7ective:
a'to $nd faults in the software
b'to prove that the software has no faults
c'to give con$dence in the software
d'to $nd performance problems
S82 )hich e,pression best matches the following characteristics of the review
processes:
1.led by the author
2.undocumented
8.no management participation
!.led by a moderator or leader
(.uses entry and e,it criteria
s'inspection
t'peer review
u'informal review
v'walk through
a's ; ! and (& t ; 8& u ; 2& v ; 1
b's ; !& t ; 8& u ; 2 and (& v ; 1
c's ; 1 and (& t ; 8& u ; 2& v ; !
d's ; ! and (& t ; 1& u; 2& v ; 8
S88 )hich of the following is CD" part of system testing0
a'business process3based testing
b'performance& load and stress testing
c'usability testing
d'top3down integration testing
S8! )hich statement about e,pected outcomes is F-HSA0
a'e,pected outcomes are de$ned by the softwareUs behavior
b'e,pected outcomes are derived from a speci$cation& not from the code
c'e,pected outcomes should be predicted before a test is run
d'e,pected outcomes may include timing constraints such as response times
S8( "he standard that gives de$nitions of testing terms is:
a'/SDQ/A9 12261
b'GS 152(31
c'-CS/Q/AAA 225
d'-CS/Q/AAA 125
S8. "he cost of $,ing a fault:
a'is not important
b'increases the later a fault is found
c'decreases the later a fault is found
d'can never be determined
S81 )hich of the following is CD" included in the "est Plan document of the "est
<ocumentation Standard0
a'what is not to be tested
b'test environment properties
c'quality plans
d'schedules and deadlines
S82 9ould reviews or inspections be considered part of testing0
a'no& because they apply to development documentation
b'no& because they are normally applied before testing
c'yes& because both help detect faults and improve quality
d'yes& because testing includes all non3constructive activities
S85 )hich of the following is not part of performance testing0
a'measuring response times
b'recovery testing
c'simulating many users
d'generating many transactions
S!6 Arror guessing is best used:
a'after more formal techniques have been applied
b'as the $rst approach to deriving test cases
c'by ine,perienced testers
d'after the system has gone live
S -
;;;;;;;;;;
1 9
2 9
8 <
! <
( 9
. -
1 G
2 -
5 9
16 <
11 G
12 G
18 <
1! 9
1( <
1. 9
11 G
12 9
15 G
26 -
21 -
22 <
28 -
2! <
2( -
2. -
21 9
22 G
25 <
86 9
81 G
82 -
88 <
8! -
8( G
8. G
81 9
82 9
85 G
!6 -
18 Oiven the following:
Switch P9 on
Start *outlook+
/F outlook appears "VAC
Send an email
9lose outlook
a' 1 test for statement coverage& 1 for branch coverage
b' 1 test for statement coverage& 2 for branch coverage
c' 1 test for statement coverage. 8 for branch coverage
d' 2 tests for statement coverage& 2 for branch coverage
e' 2 tests for statement coverage& 8 for branch coverage
1! Oiven the following code& which is true:
/F - W G "VAC
9 ; - X G
AHSA
9 ; - I G
AC</F
Jead <
/F 9 ; < "hen
Print *Arror+
AC</F
a' 1 test for statement coverage& 8 for branch coverage
b' 2 tests for statement coverage& 2 for branch coverage
c' 2 tests for statement coverage. 8 for branch coverage
d' 8 tests for statement coverage& 8 for branch coverage
e' 8 tests for statement coverage& 2 for branch coverage
1( 9onsider the following:
Pick up and read the newspaper
Hook at what is on television
/f there is a program that you are interested in watching then switch the the
television on and watch the program
Dtherwise
9ontinue reading the newspaper
/f there is a crossword in the newspaper then try and complete the crossword
a' S9 ; 1 and <9 ; 1
b' S9 ; 1 and <9 ; 2
c' S9 ; 1 and <9 ; 8
d' S9 ; 2 and <9 ; 2
e' S9 ; 2 and <9 ; 8
1. "he place to start if you want a %new' test tool is:
a' -ttend a tool e,hibition
b' /nvite a vendor to give a demo
c' -nalyse your needs and requirements
d' Find out what your budget would be for the tool
e' Search the internet
11 )hen a new testing tool is purchased& it should be used $rst by:
a' - small team to establish the best way to use the tool
b' Averyone who may eventually have some use for the tool
c' "he independent testing team
d' "he managers to see what pro7ects it should be used in
e' "he vendor contractor to write the initial scripts
12 )hat can static analysis CD" $nd0
a' "he use of a variable before it has been de$ned
b' Enreachable %*dead+' code
c' )hether the value stored in a variable is correct
d' "he re3de$nition of a variable before it has been used
e' -rray bound violations
22 "est managers should not:
a' report on deviations from the pro7ect plan
b' sign the system oK for release
c' re3allocate resource to meet original plans
d' raise incidents on faults that they have found
e' provide information for risk analysis and quality improvement
25 Enreachable code would best be found using:
a' code reviews
b' code inspections
c' a coverage tool
d' a test management tool
e' a static analysis tool
86 - tool that supports traceability& recording of incidents or scheduling of tests is
called:
a' a dynamic analysis tool
b' a test e,ecution tool
c' a debugging tool
d' a test management tool
e' a con$guration management tool
81 )hat information need not be included in a test incident report:
a' how to $, the fault
b' how to reproduce the fault
c' test environment details
d' severity& priority
e' the actual and e,pected outcomes


Suestion number 9orrect answer
1 9
2 9
8 A
! A
( 9
. -
1 G
2 G
5 9
16 A
11 G
12 G
18 G
1! G
1( A
1. 9
11 G
12 9
15 9
26 -
21 G
22 <
28 -
2! <
2( -
2. -
21 <
22 9
25 -
86 A
81 A
82 G
88 A
8! -
8( G
8. G
81 <
82 <
85 9
!6 G
1 Which of the following is a major task of test planning?
A Determining the test approach.
B Preparing test specifications.
C Evaluating exit criteria and reporting.
D Measuring and analyzing results.
2 Which of the following statements is MOST OFTEN true?
A Sourcecode inspections are often used in component testing.
B Component testing searches for defects in programs that are separately testa!le.
C Component testing is an important part of user acceptance testing.
D Component testing aims to expose pro!lems in the interactions !et"een soft"are and
hard"are components.
!n a s"stem #esigne# to work out the ta$ to %e pai#& An employee has 4000 of
salary tax free.
The next 1500 is taxed at 10%.
The next 28000 after that is taxed at 22%.
Any further amount is taxed at 40%.
To the nearest whole pound, whih of these !roups of num"ers fall into three #$%%&'&(T
e)ui*alene lasses+
A #$%%%& #'%%%& #''%%.
B #()%%*& #($%%%& #(+'%%.
C #),%%%& #),%%*& #()%%*.
D #$%%%& #$)%%& #'+%%.
' Which of the following will NOT %e #etecte# %" static anal"sis?
A Parameter type mismatches.
B Errors in re-uirements.
C .ndeclared varia!les.
D .ncalled functions.
( Which of the following test acti)ities can %e automate#? i 'e*iews and inspetions.
ii ,etris !atherin!.
iii Test plannin!.
i* Test exeution.
* #ata !eneration.
A i/ iii/ iv.
B i/ ii/ iii.
C ii/ iv/ v.
D ii/ iii/ v.
* Which of the following is an o%jecti)e of a pilot project for the intro#uction of a
testing tool?
A Evaluate testers0 competence to use the tool.
B Complete the testing of a 1ey pro2ect.
C Assess "hether the !enefits "ill !e achieved at reasona!le cost.
D Discover "hat the re-uirements for the tool are.
+ What is the M,!N purpose of a Master Test -lan?
A 3o communicate ho" incidents "ill !e managed.
B 3o communicate ho" testing "ill !e performed.
C 3o produce a test schedule.
D 3o produce a "or1 !rea1do"n structure.
.!n a /E,0T!1E approach to testing when woul# "ou e$pect the %ulk of the test
#esign work to %e %egun?
A After the soft"are or system has !een produced.
B During development.
C As early as possi!le.
D During re-uirements analysis.
2 What is the o%jecti)e of #e%ugging? i To loalise a defet.
ii To fix a defet.
iii To show *alue.
i* To inrease the ran!e of testin!.
A i/ iii.
B ii/ iii/ iv.
C ii/ iv.
D i/ ii.
13 4i)en the following #ecision ta%le
What is the e$pecte# result for each of the following test cases?A.T-1. %red is a /2
year old smo0er resident in 1ondon
2.T-/. 3ean4,ihel is a 55 year non4smo0er resident in 6aris
A A 4 5nsure/ *%6 discount/ B 4 5nsure/ no discount.
B A 4 Don0t insure/ B 4 Don0t insure.
C A 4 5nsure/ no discount/ B 4 Don0t insure.
D A 4 5nsure/ no discount/ B 4 5nsure "ith *%6 discount.
11 Which of the following are )ali# o%jecti)es for testing?
i.To find defets.
ii.To !ain onfidene in the le*el of )uality.
iii.To identify the ause of defets.
i*.To pre*ent defets.
A i/ii/ and iii.
B ii/ iii and iv.
C i/ ii and iv.
D i/iii and iv.
12 The process of #esigning test cases consists of the following acti)ities&
i. &la"orate and desri"e test ases in detail "y usin! test desi!n tehni)ues.
ii. 7peify the order of test ase exeution.
iii. Analyse re)uirements and speifiations to determine test onditions.
i*. 7peify expeted results.
,ccor#ing to the process of i#entif"ing an# #esigning tests5 what is the correct
or#er of these acti)ities?
A iii/ i/ iv/ ii.
B iii/ iv/ i/ ii.
C iii/ ii/ i/ iv.
D ii/ iii/ i/ iv.
1 What is the main purpose of impact anal"sis for testers?
A 3o determine the programming effort needed to ma1e the changes.
B 3o determine "hat proportion of the changes need to !e tested.
C 3o determine ho" much the planned changes "ill affect users.
D 3o determine ho" the existing system may !e affected !y changes.
1'Which of the following re6uirements woul# %e teste# %" a functional s"stem
test?
A 3he system must !e a!le to perform its functions for an average of )( hours '% mins per
day.
B 3he system must perform ade-uately for up to (% users.
C 3he system must allo" a user to amend the address of a customer.
D 3he system must allo" *)/%%% ne" customers per year.
1( !n a s"stem #esigne# to work out the ta$ to %e pai#&
An employee has 4000 of salary tax free.
The next 1500 is taxed at 10%.
The next 28000 after that is taxed at 22%.
Any further amount is taxed at 40%.To the nearest whole poun#5 which of these is a
)ali# 7oun#ar" 1alue ,nal"sis test case?
A #),%%%.
B #(('%*.
C #()%%*.
D #*'%%.
1* Which of the following #efines the se6uence in which tests shoul# %e e$ecute#?
A 3est plan.
B 3est procedure specification.
C 3est case specification.
D 3est design specification.
1+ 4i)en the following state transition
Which of the following series of state transitions %elow will pro)i#e 38switch
co)erage?
A A/ B/ E/ B/ C/ 7/ D.
B A/ B/ E/ B/ C/ 7/ 7.
C A/ B/ E/ B/ C/ D.
D A/ B/ C/ 7/ 7/ D.
1. 4i)en the following #ecision ta%le
8hat is the expected result for each of the follo"ing test cases9
A. 7re-uent flyer mem!er/ travelling in Business class
B. :onmem!er/ travelling in Economy class
A A 4 Don0t offer any upgrade/ B 4 Don0t offer any upgrade.
B A 4 Don0t offer any upgrade/ B 4 ;ffer upgrade to Business class.
C A 4 ;ffer upgrade to 7irst/ B 4 Don0t offer any upgrade.
D A 4 ;ffer upgrade to 7irst/ B 4 ;ffer upgrade to Business class.
12 9uring which fun#amental test process acti)it" #o we #etermine if MO/E tests
are nee#e#?
A 3est implementation and execution.
B Evaluating test exit criteria.
C 3est analysis and design.
D 3est planning and control.
23 What is the #ifference %etween a project risk an# a pro#uct risk?
A Pro2ect ris1s are potential failure areas in the soft"are or system& product ris1s are ris1s
that surround the
pro2ect0s capa!ility to deliver its o!2ectives.
B Pro2ect ris1s are the ris1s that surround the pro2ect0s capa!ility to deliver its o!2ectives&
product ris1s are
potential failure areas in the soft"are or system.
C Pro2ect ris1s are typically related to supplier issues/ organizational factors and technical
issues& product ris1s
are typically related to s1ill and staff shortages.
D Pro2ect ris1s are ris1s that delivered soft"are "ill not "or1& product ris1s are typically
related to supplier issues/
organizational factors and technical issues.
21 4i)en the following specification5 which of the following )alues for age are in
the S,ME e6ui)alence partition?
$f you are less than 18, you are too youn! to "e insured.
2etween 18 and /0 inlusi*e, you will reei*e a 20% disount.
Anyone o*er /0 is not eli!i"le for a disount.
A *</ *,/ *=.
B )=/ (%/ (*.
C *,/ )=/ (%.
D *</ )=/ (*.
21 0onsi#ering the following pseu#o8co#e5 calculate the M!N!M:M num%er of test
cases for statement co)erage5 an# the M!N!M:M num%er of test cases for #ecision
co)erage respecti)el";
'&A# A
'&A# 2
'&A# -
$% -8A T9&(
$% -82 T9&(
6'$(T :- must "e smaller than at least one num"er:
&17&
6'$(T :6roeed to next sta!e:
&(#$%
&17&
6'$(T :2 an "e smaller than -:
&(#$%
A (/ (.
B )/ (.
C )/ $.
D (/ ).
2 Which of the following is a %enefit of in#epen#ent testing?
A Code cannot !e released into production until independent testing is complete.
B 3esting is isolated from development.
C Developers do not have to ta1e as much responsi!ility for -uality.
D 5ndependent testers see other and different defects/ and are un!iased.
2' Which of the following tools is most likel" to contain a comparator? A Dynamic
Analysis tool.
B 3est Execution tool.
C Static Analysis tool.
D Security tool.
2( 4i)en the following State Ta%le&
8hich of the follo"ing represents an 5:>A?5D state transition9
A E from State S).
B E from State S(.
C B from State S*.
D 7 from State S(.
2* Which of the following is a characteristic of goo# testing in an" life c"cle
mo#el?
A All document revie"s involve the development team.
B Some/ !ut not all/ development activities have corresponding test activities.
C Each test level has test o!2ectives specific to that level.
D Analysis and design of tests !egins as soon as development is complete.
2+ Which acti)it" in the fun#amental test process inclu#es e)aluation of the
testa%ilit" of the re6uirements an# s"stem?
A 3est analysis and design.
B 3est planning and control.
C 3est closure.
D 3est implementation and execution.
2. The following statements are use# to #escri%e the %asis for creating test cases
using either %lack or white %o$ techni6ues&
i information a"out how the software is onstruted.
ii models of the system, software or omponents.
iii analysis of the test "asis doumentation.
i* analysis of the internal struture of the omponents.Which com%ination of the
statements #escri%es the %asis for %lack %o$ techni6ues?
A ii and iii.
B ii and iv.
C i and iv.
D i and iii.
22 What is t"picall" the MOST important reason to use risk to #ri)e testing efforts?
A Because testing everything is not feasi!le.
B Because ris1!ased testing is the most efficient approach to finding !ugs.
C Because ris1!ased testing is the most effective "ay to sho" value.
D Because soft"are is inherently ris1y.
3 Which of the following #efines the scope of maintenance testing?
A 3he coverage of the current regression pac1.
B 3he size and ris1 of any change@sA to the system.
C 3he time since the last change "as made to the system.
D Defects found at the last regression test run.
1 Which is the MOST important a#)antage of in#epen#ence in testing?
A An independent tester may find defects more -uic1ly than the person "ho "rote the
soft"are.
B An independent tester may !e more focused on sho"ing ho" the soft"are "or1s than the
person "ho "rote
the soft"are.
C An independent tester may !e more effective and efficient !ecause they are less familiar
"ith the soft"are
than the person "ho "rote it.
D An independent tester may !e more effective at finding defects missed !y the person "ho
"rote the soft"are.
2 For testing5 which of the options %elow %est represents the main concerns of
0onfiguration Management?
i. All items of testware are identified and *ersion ontrolled;
ii. All items of testware are used in the final aeptane test;
iii. All items of testware are stored in a ommon repository;
i*. All items of testware are tra0ed for han!e;
*. All items of testware are assi!ned to a responsi"le owner;
*i. All items of testware are related to eah other and to de*elopment items.
A i/ iv/ vi.
B ii/ iii/ v.
C i/ iii/ iv.
D iv/ v/ vi.
Which of the following woul# %e a )ali# measure of test progress?
A :um!er of undetected defects.
B 3otal num!er of defects in the product.
C :um!er of test cases not yet executed.
D Effort re-uired to fix all defects.
' Which of following statements is true? Select ,<< correct options
/egression testing shoul# %e performe#&
i one a month
ii when a defet has "een fixed
iii when the test en*ironment has han!ed
i* when the software has han!ed
A ii and iv.
B ii/ iii and iv.
C i/ ii and iii.
D i and iii.
(' 5n "hich of the follo"ing orders "ould the phases of a formal revie" usually occur9
, -lanning5 preparation5 kick off5 meeting5 rework5 follow up;
7 =ick off5 planning5 preparation5 meeting5 rework5 follow up;
0 -reparation5 planning5 kick off5 meeting5 rework5 follow up;
9 -lanning5 kick off5 preparation5 meeting5 rework5 follow up;
* Which of the following are )ali# o%jecti)es for inci#ent reports?
i. 6ro*ide de*elopers and other parties with feed"a0 a"out the pro"lem to ena"le
identifiation, isolation and orretion as neessary.
ii. 6ro*ide ideas for test proess impro*ement.
iii. 6ro*ide a *ehile for assessin! tester ompetene.
i*. 6ro*ide testers with a means of tra0in! the )uality of the system under test.
A i/ ii/ iii.
B i/ ii/ iv.
C i/ iii/ iv.
D ii/ iii/ iv.
+ 0onsi#er the following techni6ues; Which are static an# which are #"namic
techni6ues?
i. &)ui*alene 6artitionin!.
ii. <se -ase Testin!.
iii.#ata %low Analysis.
i*.&xploratory Testin!.
*. #eision Testin!.
*i $nspetions.
A iiv are static/ vvi are dynamic.
B iii and vi are static/ i/ ii/ iv and v are dynamic.
C ii/ iii and vi are static/ i/ iv and v are dynamic.
D vi is static/ iv are dynamic.
. Wh" are static testing an# #"namic testing #escri%e# as complementar"?
A Because they share the aim of identifying defects and find the same types of defect.
B Because they have different aims and differ in the types of defect they find.
C Because they have different aims !ut find the same types of defect.
D Because they share the aim of identifying defects !ut differ in the types of defect they
find.
(= 8hich of the follo"ing are disadvantages of capturing tests !y recording the actions of a
manual tester9
i The script may be unstable when unexpected events occur.
ii Data for a number of similar tests is automatically stored separately from the
script.
iii Expected results must be added to the captured script.
iv The captured script documents the exact inputs entered by the tester.
v When replaying a captured test, the tester may need to debug the script if it
doesnt play correctly.
, i5 iii5 i)5 );
7 ii5 i) an# );
0 i5 ii an# i);
9 i an# );
'3 Which of the following is #etermine# %" the le)el of pro#uct risk i#entifie#?
A Extent of testing.
B Scope for the use of test automation.
C Size of the test team.
D Be-uirement for regression testing.
,nswers
C :o Ans
*. A
). B
(. D
$. B
'. C
+. C
<. B
,. A
=. D
*%. C
**. C
*). A
*(. D
*$. C
*'. B
*+. B
*<. A
*,. C
*=. B
)%. B
)*. C
)). A
)(. D
)$. B
)'. B
)+. C
)<. A
),. A
)=. A
(%. B
(*. D
(). A
((. C
($. B
('. D
(+. B
(<. B
(,. D
(=. A
$%. A
1; 9eci#ing >ow much testing is enough shoul# take into account &8
i. 1e*el of 'is0 inludin! Tehnial and 2usiness produt and pro=et ris0
ii. 6ro=et onstraints suh as time and "ud!et
iii. 7i>e of Testin! Team
i*. 7i>e of the #e*elopment Team
aA i/ii/iii are true and iv is false
!A i//iv are true and ii is false
cA i/ii are true and iii/iv are false
dA ii/iii/iv are true and i is false
2; Test planning has which of the following major tasks?
i. #eterminin! the sope and ris0s, and identifyin! the o"=eti*es of testin!.
ii. #eterminin! the test approah ?tehni)ues,test items, o*era!e, identifyin! and
interfain! the teams in*ol*ed in testin! , testware@
iii. 'e*iewin! the Test 2asis ?suh as re)uirements,arhiteture,desi!n,interfae@
i*. #eterminin! the exit riteria.
aA i/ii/iv are true and iii is false
!A i//iv are true and ii is false
cA i/ii are true and iii/iv are false
dA ii/iii/iv are true and i is false
; E)aluating testa%ilit" of the re6uirements an# s"stem are a part of which
phase&8
aA 3est Analysis and Design
!A 3est Planning and control
cA 3est 5mplementation and execution
dA Evaluating exit criteria and reporting
'; One of the fiel#s on a form contains a te$t %o$ which accepts alpha%ets in
lower or upper case; !n#entif" the in)ali# E6ui)alance class )alue;
a. C?ASS
!. c?ASS
c. C?ass
d. C?a%*ss
(; !n a s"stem #esigne# to work out the ta$ to %e pai#&
,n emplo"ee has ?'333 of salar" ta$ free; The ne$t ?1(33 is ta$e# at 13@
The ne$t ?2.333 is ta$e# at 22@ ,n" further amount is ta$e# at '3@
Which of these groups of num%ers woul# fall into the same e6ui)alence
class?
aA #$,%%& #*$%%%& #),%%%
!A #')%%& #''%%& #),%%%
cA #),%%*& #()%%%& #('%%%
dA #',%%& #),%%%& #()%%%
*; Which of the following has highest le)el of in#epen#ence in which test
cases are &
aA Designed !y persons "ho "rite the soft"are under test
!A Designed !y a person from a different section
cA Designed !y a person from a different organization
dA Designed !y another person
+; We use the output of the re6uirement anal"sis5 the re6uirement
specification as the input for writing &8
aA .ser Acceptance 3est Cases
!A 5ntegration ?evel 3est Cases
cA .nit ?evel 3est Cases
dA Program specifications
.; 1ali#ation in)ol)es which of the following
i. 9elps to he0 the Auality of the 2uilt 6rodut
ii. 9elps to he0 that we ha*e "uilt the ri!ht produt.
iii. 9elps in de*elopin! the produt
i*. ,onitorin! tool wasta!e and o"soleteness.
aA ;ptions i/ii/iii/iv are true.
!A ii is true and i/iii/iv are false
cA i/ii/iii are true and iv is false
dA iii is true and i/ii/iv are false.
2; Which of the following uses !mpact ,nal"sis most?
aA Component testing
!A :onfunctional system testing
cA .ser acceptance testing
dA Maintenance testing
13; What is the e$pecte# result for each of the following test cases?
A. Citi!an1 card mem!er/ holding a Silver room
B. :on Citi!an1mem!er/ holding a Platinum room
aA A 4 Don0t offer any upgrade/ B 4 Don0t offer any upgrade.
!A A 4 Don0t offer any upgrade/ B 4 ;ffer upgrade to Dold.
cA A 4 ;ffer upgrade to Silver/ B 4 ;ffer upgrade to Silver.
dA A 4 ;ffer upgrade to Dold/ B 4 Don0t offer any upgrade.
11; /epeate# Testing of an alrea#" teste# program5 after mo#ification5 to
#isco)er an" #efects intro#uce# or unco)ere# as a result of the changes in
the software %eing teste# or in another relate# or unrelate# software
component&
aA Be 3esting .
!A Confirmation 3esting
cA Begression 3esting
dA :egative 3esting
12; !mpact ,nal"sis helps to #eci#e &8aA Eo" much regression testing should !e
done.
!A Exit Criteria
cA Eo" many more test cases need to "ritten.
dA Different 3ools to perform Begression 3esting
1; Functional s"stem testing is&
aA testing that the system functions "ith other systems
!A testing that the components that comprise the system function together
cA testing the end to end functionality of the system as a "hole
dA testing the system performs functions "ithin specified response times
1'; 0onsi#er the a%o)e state transition #iagram of a switch;
Which of the following represents an in)ali# state transition?
aA ;77 to ;:
!A ;: to ;77
cA 7A.?3 to ;:
1(; -eer /e)iews are also calle# as &8aA 5nspection
!A 8al1through
cA 3echnical Bevie"
dA 7ormal Bevie"
1*; 0onsi#er the following statementsF
i. 100% statement o*era!e !uarantees 100% "ranh o*era!e.
ii. 100% "ranh o*era!e !uarantees 100% statement o*era!e.
iii. 100% "ranh o*era!e !uarantees 100% deision o*era!e.
i*. 100% deision o*era!e !uarantees 100% "ranh o*era!e.
*. 100% statement o*era!e !uarantees 100% deision o*era!e.
aA ii is 3rue& i/ iii/ iv G v are 7alse
!A i G v are 3rue& ii/ iii G iv are 7alse
cA ii G iii are 3rue& i/ iv G v are 7alse
dA ii/ iii G iv are 3rue& i G v are 7alse
1+; The =ick Off phase of a formal re)iew inclu#es the following &8
aA Explaining the o!2ective
!A 7ixing defects found typically done !y author
cA 7ollo" up
dA 5ndividual Meeting preparations
1.; Match e)er" stage of the software 9e)elopment <ife c"cle with the
Testing <ife c"cle&
i. 9i4le*el desi!n a <nit tests
ii. -ode " Aeptane tests
iii. 1ow4le*el desi!n 7ystem tests
i*. 2usiness re)uirements d $nte!ration tests
aA id / iia / iiic / iv!
!A ic / iid / iiia / iv!
cA i! / iia / iiid / ivc
dA ic / iia / iiid / iv!
12; Which of the following is not phase of the Fun#amental Test -rocess?aA 3est
Planning and Control
!A 3est implementation and Execution
cA Be-uirement Analysis
dA Evaluating Exit criteria and reporting
23; Which of the following techni6ues is NOT a %lack %o$ techni6ue?
aA State transition testing
!A ?CSAH @?inear Code Se-uence and HumpA
cA syntax testing
dA !oundary value analysis
21; Success Factors for a re)iew inclu#e &
i. &ah 'e*iew does not ha*e a predefined o"=eti*e
ii. #efets found are welomed and expressed o"=eti*ely
iii. ,ana!ement supports a !ood re*iew proess.
i*. There is an emphasis on learnin! and proess impro*ement.
aA ii/iii/iv are correct and i is incorrect
!A iii / i / iv is correct and ii is incorrect
cA i / iii / iv / ii is in correct
dA ii is correct
22; 9efects #isco)ere# %" static anal"sis tools inclu#e &
i. Baria"les that are ne*er used.
ii. 7eurity *ulnera"ilities.
iii. 6ro!rammin! 7tandard Biolations
i*. <nalled funtions and proedures
aA i / ii/iii/iv is correct
!A iii /is correct 5/ii/iv are incorrect.
cA i /ii/ iii and iv are incorrect
dA iv/ ii is correct
2; Test 0on#itions are #eri)e# from &8
aA Specifications
!A 3est Cases
cA 3est Data
dA 3est Design
2'; Which of the following is true a%out White an# 7lack 7o$ Testing
Techni6ue&8
aA E-uivalance partitioning/ Decision 3a!le and Control flo" are 8hite !ox 3esting
3echni-ues.
!A E-uivalence partitioning / Boundary >alue Analysis / Data 7lo" are Blac1 Box 3esting
3echni-ues.
cA E-uivalence partitioning / State 3ransition / .se Case 3esting are !lac1 !ox 3esting
3echni-ues.
dA E-uivalence Partioning / State 3ransition / .se Case 3esting and Decision 3a!le are
8hite Box 3esting 3echni-ues.
2(; /egression testing shoul# %e performe#&
i. e*ery wee0
ii. after the software has han!ed
iii. as often as possi"le
i*. when the en*ironment has han!ed
*. when the pro=et mana!er says
aA i G ii are true/ iii/ iv G v are false
!A ii/ iii G iv are true/ i G v are false
cA ii G iv are true/ i/ iii G v are false
dA ii is true/ i/ iii/ iv G v are false
2*; 7enefits of !n#epen#ent Testing
aA 5ndependent testers are much more -ualified than Developers
!A 5ndependent testers see other and different defects and are un!iased.
cA 5ndependent 3esters cannot identify defects.
dA 5ndependent 3esters can test !etter than developers
2+; Minimum Tests /e6uire# for Statement 0o)erage an# 7ranch
0o)erage &8'ead 6
'ead A
$f pC) 8 100 then
6rint D1ar!eE
&nd if
$f p 8 50 then
6rint Dp1ar!eE
&nd if
aA Statement coverage is )/ Branch Coverage is )
!A Statement coverage is ( and !ranch coverage is )
cA Statement coverage is * and !ranch coverage is )
dA Statement Coverage is $ and Branch coverage is )
2.; Minimum Test /e6uire# for Statement 0o)erage &8#is F 0
Grder4)ty F 0
'ead Grder4)ty
$f Grder4)ty 8F20 then
#is F 0.05
$f Grder4)ty 8F100 then
#is F0.1
&nd if
&nd if
aA Statement coverage is $
!A Statement coverage is *
cA Statement coverage is (
dA Statement Coverage is )
22; The structure of an inci#ent report is co)ere# in the Stan#ar# for Software
Test 9ocumentation !EEE .22 an# is calle# as & 8
aA Anomaly Beport
!A Defect Beport
cA 3est Defect Beport
dA 3est 5ncident Beport
3; Which of the following is the task of a Test <ea# A <ea#er;
i. $nteration with the Test Tool Bendor to identify "est ways to le*era!e test tool on the
pro=et.
ii. Hrite Test 7ummary 'eports "ased on the information !athered durin! testin!
iii. #eide what should "e automated , to what de!ree and how.
i*. -reate the Test 7peifiations
aA i/ ii/ iii is true and iv is false
!A ii/iii/iv is true and i is false
cA i is true and ii/iii/iv are false
dA iii and iv is correct and i and ii are incorrect
1; Features of White 7o$ Testing Techni6ue &8i. He use expliit 0nowled!e of the
internal wor0in!s of the item "ein! tested to selet the test data.
ii. <ses speifi 0nowled!e of pro!rammin! ode to examine outputs and assumes that
the tester 0nows the path of lo!i in a unit or a pro!ram.
iii. -he0in! for the performane of the appliation
i*. Also he0s for funtionality.
aA i/ ii are true and iii and iv are false
!A iii is true and i/ii/ iv are false
cA ii /iii is true and i/iv is false
dA iii and iv are true and i/ii are false
2; Which of the following is a part of Test 0losure ,cti)ities?i. -he0in! whih
planned deli*era"les ha*e "een deli*ered
ii. #efet report analysis.
iii. %inali>in! and arhi*in! testware.
i*. Analy>in! lessons.
aA i / ii / iv are true and iii is false
!A i / ii / iii are true and iv is false
cA i / iii / iv are true and ii is false
dA All of a!ove are true
; Which of the following will %e the %est #efinition for Testing &8aA 3he goal I
purpose of testing is to demonstrate that the program "or1s.
!A 3he purpose of testing is to demonstrate that the program is defect free.
cA 3he purpose of testing is to demonstrate that the program does "hat it is supposed to
do.
dA 3esting is executing Soft"are for the purpose of finding defects.
'; Which of the following is not a t"pe of incremental testing approach?aA 3op
do"n
!A Big!ang
cA Bottom up
dA 7unctional incrementation.
(; 9ri)ers are also known as&
i. 7pade
ii. Test harness
iii. 7affoldin!aA i / ii are true and iii is false
!A i / iii are true and ii is false
cA ii / iii are true and i is false
dA All of the a!ove are true
*; E$it 0riteria ma" consist of &8i. Thorou!hness measures , suh as o*era!e of
ode, funtionality or ris0
ii. &stimates of #efet density or relia"ility measures.
iii. 'esidual ris0 suh as defets not fixed or la0 of test o*era!e in ertain areas
i*. Berifyin! the Test &n*ironment.
aA iv is correct and i/ii/iii are incorrect.
!A i/ii/iii is correct and iv is incorrect
cA ii is correct and i/ii/iii are incorrect
dA iii and iv are correct and i/ii are incorrect
+; Which of the following helps in monitoring the Test -rogress&8i. 6erenta!e
of Test -ase &xeution
ii. 6erenta!e of wor0 done in test en*ironment preparation.
iii. #efet $nformation e.!. defet density, defets found and fixed
i*. The si>e of the testin! Team and s0ills of the en!ineers
aA iv is correct and i/ii/iii are incorrect
!A i/ii/iii are correct and iv is incorrect
cA i/ii are correct and iii/iv are incorrect
dA i/iv are correct and ii / iii are incorrect
.; The selection of a test approach shoul# consi#er the conte$t &8i. 'is0 of
%ailure of the 6ro=et, ha>ards to the produt and ris0s of produt failure to humans
ii. 70ills and experiene of the people in the proposed tehni)ue, tools and methods
iii. The o"=eti*e of the testin! endea*or and the mission of the testin! team.
i*. The si>e of the testin! Team
aA i/ii/iii/iv are true
!A i/ii/iii are true and iv is false.
cA ii/iii/iv are true and i is false.
dA i/iv are true and ii/ iii are false.
2; !n case of <arge S"stems &8aA ;nly fe" tests should !e run
!A 3esting should !e on the !asis of Bis1
cA ;nly Dood 3est Cases should !e executed.
dA 3est Cases "ritten !y good test engineers should !e executed.
'3; The -ro)ision an# Management of a controlle# li%rar" containing all the
configurations items is calle# asaA Configuration Control
!A Status Accounting
cA Configuration 5dentification
dA Configuration 5dentification
Ans"ers F
* c
) a
( a
$ d
' d
+ c
< a
, !
= d
*% d
** c
*) a
*( c
*$ c
*' c
*+ d
*< a
*, d
*= c
)% !
)* a
)) a
)( a
)$ c
)' c
)+ !
)< c
), !
)= a
(% a
(* a
() c
(( d
($ !
(' c
(+ !
(< !
(, !
(= !
$% a
*. Delivera!les of test design phase include all the follo"ing except @3esting
artifactsA
aA 3est data
!A 3est data plan
cA Test summar" report
dA 3est procedure plan
). 8hich of the follo"ing is not decided in the testplanning phase9 @3esting
artifactsA
aA Schedules and delivera!les
!A Eard"are and soft"are
cA Entry and exit criteria
dA T"pes of test cases
(. 3ypical defects that are easier to find in revie"s than in dynamic testing areF
A. deviations from standards/
B.re-uirement defects/
C.design defects/
D.insufficient maintaina!ility and incorrect interface specifications.
E.All of the a!ove.
$. ?oad 3esting 3ools @Per. 3estingA
aA reduces the time spent !y the testers
!A reduces the resources spent @hard"areA
cA mostly used in "e! testing
dA all of the a%o)e
'. Bevie"s/ static analysis and dynamic testing have the same o!2ective 4
A.i#entif"ing #efects;
B. fixing defects.
C. * and )
D. :one
+. Defect arrival rate curveF
A. Shows the num%er of newl" #isco)ere# #efects per unit time
B. Sho"s the num!er of open defects per unit time.
C. Sho"s the cumulative total num!er of defects found up to this time.
D. Any of these/ depending on the company.
<. 8hat are the ) ma2or components ta1en into consideration "ith ris1 analysis9
@3est MgmtA
aA 3he pro!a!ility the negative event "ill occur
!A 3he potential loss or impact associated "ith the event
cA 7oth a an# %
dA :either a nor !
,. 8e can achieve complete statement coverage !ut still miss !ugs !ecauseF
A. 3he failure occurs only if you reach a statement ta1ing the 3B.E !ranch of an 57
statement/ and you got to the statement "ith a test that passed through the 7A?SE
!ranch.
B. 3he failure depends on the programJs ina!ility to handle specific data values/
rather than on the programJs flo" of control.
C. 7oth , an# 7
D. 8e are not re-uired to test code that customers are unli1ely to execute.
=. 8ho is responsi!le for conducting test readiness revie"9 @Performing
3estA
a. Test manager
!. 3est engineer
c. !oth A G B
d. Pro2ect Manager
*%. 8hat if the pro2ect isnJt !ig enough to 2ustify extensive testing9 @3est MgmtA
aA :se risk %ase# anal"sis to fin# out which areas nee# to %e teste#
!A .se automation tool for testing
cA a and !
dA :one of the a!ove
**. 8hat are the 1ey features to !e concentrated upon "hen doing a testing for
"orld "ide "e! sites @3est ExecutionA
aA 5nteraction !et"een html pages
!A Performance on the client side
cA Security aspects
dA ,ll of the a%o)e
*). 8hat can !e done if re-uirements are changing continuously9 @3est MgmtA
aA 8or1 "ith the pro2ectJs sta1eholders early on to understand ho"
re-uirements might change so that alternate test plans and strategies
can !e "or1ed out in advance/ if possi!le.
!A :egotiate to allo" only easilyimplemented ne" re-uirements into the
pro2ect/ "hile moving more difficult ne" re-uirements into future
versions of the application
cA 7oth a an# %
dA :one of the a!ove
*(. 3he selection of test cases for regression testing @3esting artifactsA
aA Be-uires 1no"ledge on the !ug fixes and ho" it affect the system
!A 5ncludes the area of fre-uent defects
cA 5ncludes the area "hich has undergone manyIrecent code changes
dA ,ll of the a%o)e
*$. Measurement dysfunction is a pro!lem !ecauseF
A. E)en though the num%ers "ou look at appear %etter5 to achie)e these
num%ers5 people are #oing other aspects of their work much less well;B. 8e
donJt 1no" ho" to measure a varia!le @our measurement is dysfunctionalA and
so "e donJt 1no" ho" to interpret the result.
C. Kou are measuring the "rong thing and thus reaching the "rong conclusions.
D. All of the a!ove.
*'. 8hat do you mean !y LEaving to say :;M @test planning processA
a. :o/ the pro!lem is not "ith testers
!. No5 the software is not rea#" for pro#uction
c. Both a G !
d. none of the a!ove
*+. According to the lecture/ there are several ris1s of managing your pro2ectJs
schedule
"ith a statistical relia!ility model. 3hese include @choose one or more of the
follo"ingAF
A. 3esters spend more energy early in the product trying to find !ugs than preparing
to do the rest of the pro2ectJs "or1 more efficiently
B. Managers might not realize that the testing effort is ineffective/ late in the pro2ect/
!ecause they expect a lo" rate of !ug finding/ so the lo" rate achieved doesnJt
alarm them.
C. 5t can increase the endofpro2ect pressure on testers to not find !ugs/ or to not
report !ugs.
D. ,ll of the a%o)e
*<. ;perations testing is @Performing 3estA
a. compliance testing
!. disaster testing
c. verifying compliance to rules
d. functional testing
e. ease of operations
*,. 3ools li1e change Man/ Clear case are used as @test planning processA
a. functional automation tools
!. performance testing tools
c. configuration management tools
d. none of the a!ove.
*=. 5mportant conse-uences of the impossi!ility of complete testing are @Choose one
or more ans"ersAF
A. 8e can never !e certain that the program is !ug free.
B. 8e have no definite stopping point for testing/ "hich ma1es it easier for some
managers to argue for very little testing.
C. 8e have no easy ans"er for "hat testing tas1s should al"ays !e re-uired/
!ecause every tas1 ta1es time that could !e spent on other high importance tas1s.
D. ,ll of the a%o)e;
)%. 8hich is not in se-uence in ** Step Soft"are 3esting process @3ester0s
Bole SD?CA
a Assess development plan and status
! Develop the test plan
c Test software #esign
d 3est soft"are re-uirement
)*. 5n the MASPAB case studyF
A. Security failures "ere the result of untested parts of code.
B. 3he development team achieved complete statement and !ranch coverage !ut
missed a serious !ug in the MASPAB operating system.
C. ,n error in the co#e was so o%scure that "ou ha# to test the function with
almost
e)er" input )alue to fin# its two special8case failures;
D. All of the a!ove.
)). Complete statement and !ranch coverage meansF
A. 3hat you have tested every statement in the program.
B. That "ou ha)e teste# e)er" statement an# e)er" %ranch in the program;
C. 3hat you have tested every 57 statement in the program.
D. 3hat you have tested every com!ination of values of 57 statements in the program
)(. 8hat if the pro2ect isnJt !ig enough to 2ustify extensive testing9 @3est MgmtA
aA :se risk %ase# anal"sis to fin# out which areas nee# to %e teste#
!A .se automation tool for testing
cA a and !
dA :one of the a!ove
)$. Security falls under @Performing 3estA
a. compliance testing
!. disaster testing
c. verifying compliance to rules
d. functional testing
e. ease of operations
)'. 8hich is the !est definition of complete testingF
A. Kou have discovered every !ug in the program.
B. Kou have tested every statement/ !ranch/ and com!ination of !ranches in the
program.
C. Kou have completed every test in the test plan.
D. Bou ha)e reache# the sche#ule# ship #ate;
)+. 8hat is the concept of introducing a small change to the program and having the
effects of that change sho" up in some test9 @3esting conceptsA
aA Des1 chec1ing
!A De!ugging a program
cA A mutation error
dA Performance testing
eA !ntro#ucing mutations
5S3CB 7oundation ?evel Moc1 3est )
DurationF * hour
5nstructionsF
*. Pass criteria "ill !e +%6
). :o negative mar1ing
*. C;3S is 1no"n as
A. Commercial off the shelf soft"are
B. Compliance of the soft"are
C. Change control of the soft"are
D. Capa!le off the shelf soft"are
). 7rom the !elo" given choices/ "hich one is the NConfidence testing0
A. Sanity testing
B. System testing
C. Smo1e testing
D. Begression testing
(. NDefect Density0 calculated in terms of
A. 3he num!er of defects identified in a component or system divided !y the size of
the component or the system
B. 3he num!er of defects found !y a test phase divided !y the num!er found !y that
test phase and any other means after "ards
C. 3he num!er of defects identified in the component or system divided !y the
num!er of defects found !y a test phase
D. 3he num!er of defects found !y a test phase divided !y the num!er found !y the
size of the system
$. NBe !ugging0 is 1no"n as
A. Preventing the defects !y inspection
B. 7ixing the defects !y de!ugging
C. Adding 1no"n defects !y seeding
D. A process of fixing the defects !y tester
'. An expert !ased test estimation is also 1no"n as
A. :arro" !and Delphi
B. 8ide !and Delphi
C. Bespo1e Delphi
D. Bo!ust Delphi
+. 8hen testing a grade calculation system/ a tester determines that all scores from
=% to *%% "ill yield a grade of A/ !ut scores !elo" =% "ill not. 3his analysis is 1no"n
asF
A. E-uivalence partitioning
B. Boundary value analysis
C. Decision ta!le
D. Ey!rid analysis
<. All of the follo"ing might !e done during unit testing except
A. Des1 chec1
B. Manual support testing
C. 8al1through
D. Compiler !ased testing
=. 8hich of the follo"ing characteristics is primarily associated "ith soft"are
reusa!ility9
A. 3he extent to "hich the soft"are can !e used in other applications
B. 3he extent to "hich the soft"are can !e used !y many different users
C. 3he capa!ility of the soft"are to !e moved to a different platform
D. 3he capa!ility of one system to !e coupled "ith another system
*%. 8hich of the follo"ing soft"are change management activities is most vital to
assessing the impact of proposed soft"are modifications9
A. Baseline identification B. Configuration auditing
C. Change control D. >ersion control
**. 8hich of the follo"ing statements is true a!out a soft"are verification and
validation program9
5. 5t strives to ensure that -uality is !uilt into soft"are.
55. 5t provides management "ith insights into the state of a soft"are pro2ect.
555. 5t ensures that alpha/ !eta/ and system tests are performed.
5>. 5t is executed in parallel "ith soft"are development activities.
A. 5/ 55G555 B.55/ 555G5> C.5/ 55G5> D.5/ 555G5>
*). 8hich of the follo"ing is a re-uirement of an effective soft"are environment9
5. Ease of use
55. Capacity for incremental implementation
555. Capa!ility of evolving "ith the needs of a pro2ect
5>. 5nclusion of advanced tools
A.5/ 55 G555 B.5/ 55 G5> C.55/ 555G5> D.5/ 555G5>
*(. A test manager "ants to use the resources availa!le for the automated testing of
a "e! application. 3he !est choice is
A. 3est automater/ "e! specialist/ DBA/ test lead
B. 3ester/ test automater/ "e! specialist/ DBA
C. 3ester/ test lead/ test automater/ DBA
D. 3ester/ "e! specialist/ test lead/ test automater
*$. A pro2ect manager has !een transferred to a ma2or soft"are development pro2ect
that is in the implementation phase. 3he highest priority for this pro2ect manager
should !e to
B. Esta!lish a relationship "ith the customer
C. ?earn the pro2ect o!2ectives and the existing pro2ect plan
D. Modify the pro2ect0 s organizational structure to meet the manager0 s
management style
E. Ensure that the pro2ect proceeds at its current pace
*'. Change O re-uires a higher level of authority than Change K in "hich of the
follo"ing pairs9
Change O Change K
A. Code in development Code in production
B. Specifications during re-uirements analysis Specifications during systems test
C. Documents re-uested !y the technical development group Documents re-uested
!y customers
D. A product distri!uted to several sites A product "ith a single user
*+. 8hich of the follo"ing functions is typically supported !y a soft"are -uality
information system9
5. Becord 1eeping
55. System design
555. Evaluation scheduling
5>. Error reporting
A.5/ 55G555 B.55/ 555 G5> C.5/ 555 G5> D.5/ 55 G 5>
*<. During the testing of a module tester NO0 finds a !ug and assigned it to developer.
But developer re2ects the same/ saying that it0s not a !ug. 8hat NO0 should do9
A. Beport the issue to the test manager and try to settle "ith the developer.
B. Betest the module and confirm the !ug
C. Assign the same !ug to another developer
D. Send to the detailed information of the !ug encountered and chec1 the
reproduci!ility
*,. 3he primary goal of comparing a user manual "ith the actual !ehavior of the
running program during system testing is to
A. 7ind !ugs in the program
B. Chec1 the technical accuracy of the document
C. Ensure the ease of use of the document
D. Ensure that the program is the latest version
*=. A type of integration testing in "hich soft"are elements/ hard"are elements/ or
!oth are com!ined all at once into a component or an overall system/ rather than in
stages.
A. System 3esting B. BigBang 3esting
C. 5ntegration 3esting D. .nit 3esting
)%. 5n practice/ "hich ?ife Cycle model may have more/ fe"er or different levels of
development and testing/ depending on the pro2ect and the soft"are product. 7or
example/ there may !e component integration testing after component testing/ and
system integration testing after system testing.
A. 8ater 7all Model B.>Model
C. Spiral Model D. BAD Model
)*. 8hich techni-ue can !e used to achieve input and output coverage9 5t can !e
applied to human input/ input via interfaces to a system/ or interface parameters in
integration testing.
A. Error Duessing B. Boundary >alue Analysis
C. Decision 3a!le testing D. E-uivalence partitioning
)). 3here is one application/ "hich runs on a single terminal. 3here is another
application that "or1s on multiple terminals. 8hat are the test techni-ues you "ill
use on the second application that you "ould not do on the first application9
A. 5ntegrity/ Besponse time B. Concurrency test/ Scala!ility
C. .pdate G Boll!ac1/ Besponse time D. Concurrency test/ 5ntegrity
)(. Kou are the test manager and you are a!out the start the system testing. 3he
developer team says that due to change in re-uirements they "ill !e a!le to deliver
the system to you for testing ' "or1ing days after the due date. Kou can not change
the resources@"or1 hours/ test tools/ etc.A 8hat steps you "ill ta1e to !e a!le to
finish the testing in time. @
A. 3ell to the development team to deliver the system in time so that testing activity
"ill !e finish in time.
B. Extend the testing plan/ so that you can accommodate the slip going to occur
C. Ban1 the functionality as per ris1 and concentrate more on critical functionality
testing
D. Add more resources so that the slippage should !e avoided
)$. 5tem transmittal report is also 1no"n as
A. 5ncident report B. Belease note
C. Bevie" report D. Audit report
)'. 3esting of soft"are used to convert data from existing systems for use in
replacement systems
A. Data driven testing B. Migration testing
C. Configuration testing D. Bac1 to !ac1 testing
)+. Big !ang approach is related to
A. Begression testing B. 5nter system testing
C. Betesting D. 5ntegration testing
)<. Cause effect graphing is related to the standard
A. BS<<== B. BS <=)'I) C. 5S;I5EC =)+I* D. 5S;I5EC )(,)I*
),. L3he tracing of re-uirements for a test level through the layers of a test
documentationM done !y
A. Eorizontal trace!ility B. Depth trace!ility
C. >ertical trace!ility D. Eorizontal G >ertical trace!ilities
)=. A test harness is a
A. A high level document descri!ing the principles/ approach and ma2or o!2ectives of
the organization regarding testing
B. A distance set of test activities collected into a managea!le phase of a pro2ect
C. A test environment comprised of stu!s and drives needed to conduct a test
D. A set of several test cases for a component or system under test
(%. Kou are a tester for testing a large system. 3he system data model is very large
"ith many attri!utes and there are a lot of inter dependencies "ith in the fields.
8hat steps "ould you use to test the system and also "hat are the efforts of the test
you have ta1en on the test plan
A. 5mprove super vision/ More revie"s of artifacts or program means stage
containment of the defects.
B. Extend the test plan so that you can test all the inter dependencies
C. Divide the large system in to small modules and test the functionality
D. 3est the interdependencies first/ after that chec1 the system as a "hole
(*. Change re-uest should !e su!mitted through development or program
management. A change re-uest must !e "ritten and should include the follo"ing
criteria.
5. Definition of the change
55. Documentation to !e updated
555. :ame of the tester or developer
5>. Dependencies of the change re-uest.
A. 5/ 555 and 5> B. 5/ 55 and 555 C. 55/ 555 and 5> D. 5/ 55 and 5>
(). NEntry criteria0 should address -uestions such as
5. Are the necessary documentation/ design and re-uirements information availa!le
that "ill allo" testers to operate the system and 2udge correct !ehavior.
55. 5s the test environmentla!/ hard"are/ soft"are and system administration
support ready9
555. 3hose conditions and situations that must prevail in the testing process to allo"
testing to continue effectively and efficiently.
5>. Are the supporting utilities/ accessories and prere-uisites availa!le in forms that
testers can use
A. 5/ 55 and 5> B. 5/ 55 and 555 C. 5/ 55/ 555 and 5> D. 55/ 555 and 5>.
((. L3his life cycle model is !asically driven !y schedule and !udget ris1sM 3his
statement is !est suited for
A. 8ater fall model B. Spiral model
C. 5ncremental model D. >Model
($. 3he !ug trac1ing system "ill need to capture these phases for each !ug.
5. Phase in2ected
55. Phase detected
555. Phase fixed
5>. Phase removed
A. 5/ 55 and 555 B. 5/ 55 and 5> C. 55/ 555 and 5> D. 5/ 555 and 5>
('. ;ne of the more daunting challenges of managing a test pro2ect is that so many
dependencies converge at test execution. ;ne missing configuration file or hard "are
device can render all your test results meaning less. Kou can end up "ith an entire
platoon of testers sitting around for days.
8ho is responsi!le for this incident9
A. 3est managers faults only
B. 3est lead faults only
C. 3est manager and pro2ect manager faults
D. 3esters faults only
(+. System test can !egin "hen9
5. 3he test team competes a three day smo1e test and reports on the results to the system
test phase entry meeting
55. 3he development team provides soft"are to the test team ( !usiness days prior to
starting of the system testing
555. All components are under formal/ automated configuration and release management
control
A. 5 and 55 only B. 55 and 555 only C. 5 and 555 only D. 5/ 55 and 555
(<. 3est charters are used in PPPPPPPP testing
A. Exploratory testing B. .sa!ility testing
C. Component testing D. Maintaina!ility testing
All 3he Best
5S3CB 7oundation ?evel Moc1 3est ) Qey
C.:o Ans"er C.:o Ans"er
* @AA )% @BA
) @CA )* @DA
( @AA )) @CA
$ @CA )( @CA
' @BA )$ @BA
+ @AA )' @BA
< @BA )+ @DA
, @BA )< @BA
= @AA ), @AA
*% @CA )= @CA
** @CA (% @AA
*) @AA (* @DA
*( @BA () @AA
*$ @BA (( @DA
*' @DA ($ @BA
*+ @CA (' @AA
*< @DA (+ @DA
*, @BA (< @AA
*= @BA
5S3CB 7oundation ?evel Moc1 3est *
DurationF * hour
5nstructionsF
*. Pass criteria "ill !e +%6 /
). :o negative mar1ing
*. PPPPPPPPPPP 3esting "ill !e performed !y the people at client o"n locations @*MA
A. Alpha testing B. 7ield testing C. Performance testing D. System testing
). System testing should investigate @)MA
A. :onfunctional re-uirements only not 7unctional re-uirements
B. 7unctional re-uirements only not nonfunctional re-uirements
C. :onfunctional re-uirements and 7unctional re-uirements
D. :onfunctional re-uirements or 7unctional re-uirements
(. 8hich is the nonfunctional testing @*MA
A. Performance testing B. .nit testing
C. Begression testing D. Sanity testing
$. 8ho is responsi!le for document all the issues/ pro!lems and open point that "ere
identified during the revie" meeting @)MA
A. Moderator B. Scri!e C. Bevie"ers D. Author
'. 8hat is the main purpose of 5nformal revie" @)MA
A. 5nexpensive "ay to get some !enefit
B. 7ind defects
C. ?earning/ gaining understanding/ effect finding
D. Discuss/ ma1e decisions/ solve technical pro!lems
+. Purpose of test design techni-ue is @*MA
A. 5dentifying test conditions only/ not 5dentifying test cases
B. :ot 5dentifying test conditions/ 5dentifying test cases only
C. 5dentifying test conditions and 5dentifying test cases
D. 5dentifying test conditions or 5dentifying test cases
<. PPPPPPPPPPP techni-ue can !e used to achieve input and output coverage @*MA
A. Boundary value analysis B. E-uivalence partitioning
C. Decision ta!le testing D. State transition testing
,. .se cases can !e performed to test @)MA
A. Performance testing B. .nit testing
C. Business scenarios D. Static testing
=. PPPPPPPPPPPPPPPP testing is performed at the developing organization0s site @*MA
A. .nit testing B. Begression testing
C. Alpha testing D. 5ntegration testing
*%. 3he purpose of exit criteria is @)MA
A. Define "hen to stop testing
B. End of test level
C. 8hen a set of tests has achieved a specific pre condition
D. All of the a!ove
**. 8hich is not the pro2ect ris1s @)MA
A. Supplier issues B. ;rganization factors
C. 3echnical issues D. Errorprone soft"are delivered
*). Poor soft"are characteristics are @(MA
A. ;nly Pro2ect ris1s
B. ;nly Product ris1s
C. Pro2ect ris1s and Product ris1s
D. Pro2ect ris1s or Product ris1s
*(. PPPPPPPP and PPPPPPPP are used "ithin individual "or1!enches to produce the right
output products. @)MA
A. 3ools and techni-ues B. Procedures and standards
C. Processes and "al1throughs D. Bevie"s and update
*$. 3he soft"are engineerJs role in tool selection is @(MA
A. 3o identify/ evaluate/ and ran1 tools/ and recommend tools to management
B. 3o determine "hat 1ind of tool is needed/ then find it and !uy it
C. 3o initiate the tool search and present a case to management
D. 3o identify/ evaluate and select the tools
*'. A PPPPP is the step!ystep method follo"ed to ensure that standards are met @)MA
A. SD?C B. Pro2ect Plan C. Policy D. Procedure
*+. 8hich of the follo"ing is the standard for the Soft"are product -uality @*MA
A. 5S; *=)+ B. 5S; ,)= C. 5S; *%*) D. 5S; *%),
*<. 8hich is not the testing o!2ectives @*MA
A. 7inding defects
B. Daining confidence a!out the level of -uality and providing information
C. Preventing defects.
D. De!ugging defects
*,. Bug life cycle @*MA
A. ;pen/ Assigned/ 7ixed/ Closed
B. ;pen/ 7ixed/ Assigned/ Closed
C. Assigned/ ;pen/ Closed/ 7ixed
D. Assigned/ ;pen/ 7ixed/ Closed
*=. 8hich is not the soft"are characteristics @*MA
A. Belia!ility B. .sa!ility C. Scala!ility D. Maintaina!ility
)%. 8hich is not a testing principle @)MA
A. Early testing B. Defect clustering
C. Pesticide paradox D. Exhaustive testing
)*. NO0 has given a data on a person age/ "hich should !e !et"een * to ==. .sing B>A
"hich is the appropriate one @(MA
A. %/*/)/== B. */ ==/ *%%/ =, C. %/ */ ==/ *%% D. 4*/ %/ */ ==
)). 8hich is not the fundamental test process @*MA
A. Planning and control B. 3est closure activities
C. Analysis and design D. :one
)(. 8hich is not a Component testing @)MA
A. Chec1 the memory lea1s B. Chec1 the ro!ustness
C. Chec1 the !ranch coverage D. Chec1 the decision ta!les
)$. PDCA is 1no"n as @*MA
A. Plan/ Do/ Chec1/ Act B. Plan/ Do/ Correct/ Act
C. Plan/ De!ug/ Chec1/ Act D. Plan/ Do/ Chec1/ Accept
)'. Contract and regulation testing is a part of @)MA
A. System testing B. Acceptance testing
C. 5ntegration testing D. Smo1e testing
)+. 8hich is not a !lac1 !ox testing techni-ue @*MA
A. E-uivalence partition B. Decision ta!les
C. 3ransaction diagrams D. Decision testing
)<. Arc testing is 1no"n as @)MA
A. Branch testing B. Agile testing
C. Beta testing D. Adhoc testing
),. A soft"are model that can0t !e used in functional testing @)MA
A. Process flo" model B. State transaction model
C. Menu structure model D. Plain language specification model
)=. 7ind the mismatch @)MA
A. 3est data preparation tools 4 Manipulate Data !ases
B. 3est design tools 4 Denerate test inputs
C. Be-uirement management tools 4 Ena!les individual tests to !e tracea!le
D. Configuration management tools 4 Chec1 for consistence
(%. 3he principle of Cyclomatic complexity/ considering ? as edges or lin1s/ : as nodes/ P as
independent paths @)MA
A. ?: R)P
B. :? R)P
C. :? RP
D. :? RP
(*. 7PA is used to @)MA
A. 3o measure the functional re-uirements of the pro2ect
B. 3o measure the size of the functionality of an 5nformation system
C. 3o measure the functional testing effort
D. 3o measure the functional flo"
(). 8hich is not a test ;racle @)MA
A. 3he existing system @7or a !ench mar1A
B. 3he code
C. 5ndividual0s 1no"ledge
D. .ser manual
((. 7ind the correct flo" of the phases of a formal revie" @(MA
A. Planning/ Bevie" meeting/ Be"or1/ Qic1 off
B. Planning/ 5ndividual preparation/ Qic1 off/ Be"or1
C. Planning/ Bevie" meeting/ Be"or1/ 7ollo" up
D. Planning/ 5ndividual preparation/ 7ollo" up/ Qic1 off
($. Stochastic testing using statistical information or operational profiles uses the follo"ing
method @(MA
A. Eeuristic testing approach
B. Methodical testing approach
C. Model !ased testing approach
D. Process or standard compliant testing approach
('. A pro2ect that is in the implementation phase is six "ee1s !ehind schedule. 3he delivery
date for the product is four months a"ay. 3he pro2ect is not allo"ed to slip the delivery date
or compromise on the -uality standards esta!lished for this product. 8hich of the follo"ing
actions "ould !ring this pro2ect !ac1 on schedule9 @(MA
A. Eliminate some of the re-uirements that have not yet !een implemented.
B. Add more engineers to the pro2ect to ma1e up for lost "or1.
C. As1 the current developers to "or1 overtime until the lost "or1 is recovered.
D. Eire more soft"are -uality assurance personnel.
(+. ;ne person has !een dominating the current soft"are process improvement meeting.
8hich of the follo"ing techni-ues should the facilitator use to !ring other team mem!ers
into the discussion9 @(MA
A. Confront the person and as1 that other team mem!ers !e allo"ed to express their
opinions.
B. 8ait for the person to pause/ ac1no"ledge the person0 s opinion/ and as1 for someone
else0 s opinion.
C. S"itch the topic to an issue a!out "hich the person does not have a strong opinion.
D. Express an opinion that differs from the person0 s opinion in order to encourage others to
express their ideas.
(<. Maintenance releases and technical assistance centers are examples of "hich of the
follo"ing costs of -uality9 @(MA
A. External failure
B. 5nternal failure
C. Appraisal
D. Prevention
All the !est
5S3CB 7oundation ?evel Moc1 3est * Qey
C.:o Ans"er C.:o Ans"er
* B )% D
) C )* C
( A )) D
$ B )( D
' A )$ A
+ C )' B
< B )+ D
, C )< A
= C ), C
*% D )= D
** D (% A
*) B (* B
*( B () B
*$ A (( C
*' D ($ C
*+ A (' A
*< D (+ B
*, A (< A
*= C
* 8e split testing into distinct stages primarily !ecauseF
aA Each test stage has a different purpose.
!A 5t is easier to manage testing in stages.
cA 8e can run different tests in different environments.
dA 3he more stages "e have/ the !etter the testing.
) 8hich of the follo"ing is li1ely to !enefit most from the use of test tools providing test
capture and replay facilities9
aA Begression testing
!A 5ntegration testing
cA System testing
dA .ser acceptance testing
( 8hich of the follo"ing statements is :;3 correct9
aA A minimal test set that achieves *%%6 ?CSAH coverage "ill also achieve *%%6 !ranch
coverage.
!A A minimal test set that achieves *%%6 path coverage "ill also achieve *%%6 statement
coverage.
cA A minimal test set that achieves *%%6 path coverage "ill generally detect more faults
than one that achieves *%%6 statement coverage.
dA A minimal test set that achieves *%%6 statement coverage "ill generally detect more
faults than one that achieves *%%6 !ranch coverage.
$ 8hich of the follo"ing re-uirements is testa!le9
aA 3he system shall !e user friendly.
!A 3he safetycritical parts of the system shall contain % faults.
cA 3he response time shall !e less than one second for the specified design load.
dA 3he system shall !e !uilt to !e porta!le.
' Analyse the follo"ing highly simplified procedureF
As1F L8hat type of tic1et do you re-uire/ single or return9M
57 the customer "ants Nreturn0
As1F L8hat rate/ Standard or Cheapday9M
57 the customer replies NCheapday0
SayF L3hat "ill !e #**F)%M
E?SE
SayF L3hat "ill !e #*=F'%M
E:D57
E?SE
SayF L3hat "ill !e #=F<'M
E:D57
:o" decide the minimum num!er of tests that are needed to ensure that all
the -uestions have !een as1ed/ all com!inations have occurred and all
replies given.
aA (
!A $
cA 'dA +
+ Error guessingF
aA supplements formal test design techni-ues.
!A can only !e used in component/ integration and system testing.
cA is only performed in user acceptance testing.
dA is not repeata!le and should not !e used.
< 8hich of the follo"ing is :;3 true of test coverage criteria9
aA 3est coverage criteria can !e measured in terms of items exercised !y a test suite.
!A A measure of test coverage criteria is the percentage of user re-uirements covered.
cA A measure of test coverage criteria is the percentage of faults found.
dA 3est coverage criteria are often used "hen specifying test completion criteria.
, 5n prioritising "hat to test/ the most important o!2ective is toF
aA find as many faults as possi!le.
!A test high ris1 areas.
cA o!tain good test coverage.
dA test "hatever is easiest to test.
= Diven the follo"ing sets of test management terms @vzA/ and activity descriptions @*'A/
"hich one of the follo"ing !est pairs the t"o sets9
v 4 test control
" 4 test monitoring
x test estimation
y incident management
z configuration control
* calculation of re-uired test resources
) maintenance of record of test results
( reallocation of resources "hen tests overrun
$ report on deviation from test plan
' trac1ing of anomalous test results
aA v(/")/x*/y'/z$
!A v)/"'/x*/y$/z(
cA v(/"$/x*/y'/z)
dA v)/"*/x$/y(/z'
*% 8hich one of the follo"ing statements a!out system testing is :;3 true9
aA System tests are often performed !y independent teams.
!A 7unctional testing is used more than structural testing.
cA 7aults found during system tests can !e very expensive to fix.
dA Endusers should !e involved in system tests.
** 8hich of the follo"ing is false9
aA 5ncidents should al"ays !e fixed.
!A An incident occurs "hen expected and actual results differ.
cA 5ncidents can !e analysed to assist in test process improvement.
dA An incident can !e raised against documentation.
*) Enough testing has !een performed "henF
aA time runs out.
!A the re-uired level of confidence has !een achieved.
cA no more faults are found.
dA the users "on0t find any serious faults.
*( 8hich of the follo"ing is :;3 true of incidents9
aA 5ncident resolution is the responsi!ility of the author of the soft"are under test.
!A 5ncidents may !e raised against user re-uirements.
cA 5ncidents re-uire investigation andIor correction.
dA 5ncidents are raised "hen expected and actual results differ.
*$ 8hich of the follo"ing is not descri!ed in a unit test standard9
aA syntax testing
!A e-uivalence partitioning
cA stress testing
dA modified conditionIdecision coverage
*' 8hich of the follo"ing is false9
aA 5n a system t"o different failures may have different severities.
!A A system is necessarily more relia!le after de!ugging for the removal of a fault.
cA A fault need not affect the relia!ility of a system.
dA .ndetected errors may lead to faults and eventually to incorrect !ehaviour.
*+ 8hich one of the follo"ing statements/ a!out capturereplay tools/ is :;3 correct9
aA 3hey are used to support multiuser testing.
!A 3hey are used to capture and animate user re-uirements.
cA 3hey are the most fre-uently purchased types of CAS3 tool.
dA 3hey capture aspects of user !ehaviour.
*< Eo" "ould you estimate the amount of retesting li1ely to !e re-uired9
aA Metrics from previous similar pro2ects
!A Discussions "ith the development team
cA 3ime allocated for regression testing
dA a G !
*, 8hich of the follo"ing is true of the >model9
aA 5t states that modules are tested against user re-uirements.
!A 5t only models the testing phase.
cA 5t specifies the test techni-ues to !e used.
dA 5t includes the verification of designs.
*= 3he oracle assumptionF
aA is that there is some existing system against "hich test output may !e chec1ed.
!A is that the tester can routinely identify the correct outcome of a test.
cA is that the tester 1no"s everything a!out the soft"are under test.
dA is that the tests are revie"ed !y experienced testers.
)% 8hich of the follo"ing characterises the cost of faults9
aA 3hey are cheapest to find in the early development phases and the most expensive to fix
in the latest test phases.
!A 3hey are easiest to find during system testing !ut the most expensive to fix then.
cA 7aults are cheapest to find in the early development phases !ut the most expensive to fix
then.
dA Although faults are most expensive to find during early development phases/ they are
cheapest to fix then.
)* 8hich of the follo"ing should :;3 normally !e an o!2ective for a test9
aA 3o find faults in the soft"are.
!A 3o assess "hether the soft"are is ready for release.
cA 3o demonstrate that the soft"are doesn0t "or1.
dA 3o prove that the soft"are is correct.
)) 8hich of the follo"ing is a form of functional testing9
aA Boundary value analysis
!A .sa!ility testing
cA Performance testing
dA Security testing
)( 8hich of the follo"ing "ould :;3 normally form part of a test plan9
aA 7eatures to !e tested
!A 5ncident reports
cA Bis1s
dA Schedule
)$ 8hich of these activities provides the !iggest potential cost saving from the use of
CAS39
aA 3est management
!A 3est design
cA 3est execution
dA 3est planning
)' 8hich of the follo"ing is :;3 a "hite !ox techni-ue9
aA Statement testing
!A Path testing
cA Data flo" testing
dA State transition testing
)+ Data flo" analysis studiesF
aA possi!le communications !ottlenec1s in a program.
!A the rate of change of data values as a program executes.
cA the use of data on paths through the code.
dA the intrinsic complexity of the code.
)< 5n a system designed to "or1 out the tax to !e paidF
An employee has #$%%% of salary tax free. 3he next #*'%% is taxed at *%6
3he next #),%%% is taxed at ))6
Any further amount is taxed at $%6
3o the nearest "hole pound/ "hich of these is a valid Boundary >alue Analysis test case9
aA #*'%%
!A #()%%*
cA #(('%*
dA #),%%%
), An important !enefit of code inspections is that theyF
aA ena!le the code to !e tested !efore the execution environment is ready.
!A can !e performed !y the person "ho "rote the code.
cA can !e performed !y inexperienced staff.
dA are cheap to perform.
)= 8hich of the follo"ing is the !est source of Expected ;utcomes for .ser Acceptance 3est
scripts9
aA Actual results
!A Program specification
cA .ser re-uirements
dA System specification
(% 8hat is the main difference !et"een a "al1through and an inspection9
aA An inspection is lead !y the author/ "hilst a "al1through is lead !y a trained moderator.
!A An inspection has a trained leader/ "hilst a "al1through has no leader.
cA Authors are not present during inspections/ "hilst they are during "al1throughs.
dA A "al1through is lead !y the author/ "hilst an inspection is lead !y a trained moderator.
(* 8hich one of the follo"ing descri!es the ma2or !enefit of verification early in the life
cycle9
aA 5t allo"s the identification of changes in user re-uirements.
!A 5t facilitates timely set up of the test environment.
cA 5t reduces defect multiplication.
dA 5t allo"s testers to !ecome involved early in the pro2ect.
() 5ntegration testing in the smallF
aA tests the individual components that have !een developed.
!A tests interactions !et"een modules or su!systems.
cA only uses components that form part of the live system.
dA tests interfaces to other systems.
(( Static analysis is !est descri!ed asF
aA the analysis of !atch programs.
!A the revie"ing of test plans.
cA the analysis of program code.
dA the use of !lac1 !ox testing.
($ Alpha testing isF
aA postrelease testing !y end user representatives at the developer0s site.
!A the first testing that is performed.
cA prerelease testing !y end user representatives at the developer0s site.
dA prerelease testing !y end user representatives at their sites.
(' A failure isF
aA found in the soft"are& the result of an error.
!A departure from specified !ehaviour.
cA an incorrect step/ process or data definition in a computer program.
dA a human action that produces an incorrect result.
(+ 5n a system designed to "or1 out the tax to !e paidF
An employee has #$%%% of salary tax free. 3he next #*'%% is taxed at *%6
3he next #),%%% is taxed at ))6
Any further amount is taxed at $%6
8hich of these groups of num!ers "ould fall into the same e-uivalence class9
aA #$,%%& #*$%%%& #),%%%
!A #')%%& #''%%& #),%%%
cA #),%%*& #()%%%& #('%%%
dA #',%%& #),%%%& #()%%%
(< 3he most important thing a!out early test design is that itF
aA ma1es test preparation easier.
!A means inspections are not re-uired.
cA can prevent fault multiplication.
dA "ill find all faults.
(, 8hich of the follo"ing statements a!out revie"s is true9
aA Bevie"s cannot !e performed on user re-uirements specifications.
!A Bevie"s are the least effective "ay of testing code.
cA Bevie"s are unli1ely to find faults in test plans.
dA Bevie"s should !e performed on specifications/ code/ and test plans.
(= 3est cases are designed duringF
aA test recording.
!A test planning.
cA test configuration.
dA test specification.
$% A configuration management system "ould :;3 normally provideF
aA lin1age of customer re-uirements to version num!ers.
!A facilities to compare test results "ith expected results.
cA the precise differences in versions of soft"are component source code.
dA restricted access to the source code li!rary.
Cuestion num!er Correct ans"er
* A
) A
( D
$ C
' A
+ A
< C
, B
= C
*% D
** A
*) B
*( A
*$ C
*' B
*+ B
*< D
*, D
*= B
)% A
)* D
)) A
)( B
)$ C
)' D
)+ C
)< C
), A
)= C
(% D
(* C
() B
(( C
($ C
(' B
(+ D
(< C
(, D
(= D
$% B
*. An input field ta1es the year of !irth !et"een *=%% and )%%$
3he !oundary values for testing this field are
a. %/*=%%/)%%$/)%%'
!. *=%%/ )%%$
c. *,==/*=%%/)%%$/)%%'
d. *,==/ *=%%/ *=%*/)%%(/)%%$/)%%'
). 8hich one of the follo"ing are nonfunctional testing methods9
a. System testing
!. .sa!ility testing
c. Performance testing
d. Both ! G c
(. 8hich of the follo"ing tools "ould !e involved in the automation of regression
test9
a. Data tester
!. Boundary tester
c. CaptureIPlay!ac1
d. ;utput comparator.
$. 5ncorrect form of ?ogic coverage isF
a. Statement Coverage
!. Pole Coverage
c. Condition Coverage
d. Path Coverage
'. 8hich of the follo"ing is not a -uality characteristic listed in 5S; =*)+ Standard9
a. 7unctionality
!. .sa!ility
c. Supporta!ility
d. Maintaina!ility
+. 3o test a function/ the programmer has to "rite a PPPPPPPPP/ "hich calls the
function to !e tested and passes it test data.
a. Stu!
!. Driver
c. Proxy
d. :one of the a!ove
<. Boundary value testing
a. 5s the same as e-uivalence partitioning tests
!. 3est !oundary conditions on/ !elo" and a!ove the edges of input and output
e-uivalence classes
c. 3ests com!inations of input circumstances
d. 5s used in "hite !ox testing strategy
,. Pic1 the !est definition of -uality
a. Cuality is 2o! one
!. Sero defects
c. Conformance to re-uirements
d. 8or1 as designed
=. 7ault Mas1ing is
a. Error condition hiding another error condition
!. Creating a test case "hich does not reveal a fault
c. Mas1ing a fault !y developer
d. Mas1ing a fault !y a tester
*%. ;ne Qey reason "hy developers have difficulty testing their o"n "or1 is F
a. ?ac1 of technical documentation
!. ?ac1 of test tools on the mar1et for developers
c. ?ac1 of training
d. ?ac1 of ;!2ectivity
**. During the soft"are development process/ at "hat point can the test process
start9
a. 8hen the code is complete.
!. 8hen the design is complete.
c. 8hen the soft"are re-uirements have !een approved.
d. 8hen the first code module is ready for unit testing
*). 5n a revie" meeting a moderator is a person "ho
a. 3a1es minutes of the meeting
!. Mediates !et"een people
c. 3a1es telephone calls
d. 8rites the documents to !e revie"ed
*(. Diven the 7ollo"ing program
57 O T K
3EE: Statement *&
E?SE 57 K UV S
3EE: Statement )&
E:D
McCa!e0s Cyclomatic Complexity is F
a. )
!. (
c. $
d. '
*$. Eo" many test cases are necessary to cover all the possi!le se-uences of
statements @pathsA for the follo"ing program fragment9 Assume that the t"o
conditions are independent of each other F
WWWW
if @Condition *A
then statement *
else statement )
fi
if @Condition )A
then statement (
fi
WWWW
a. ) 3est Cases
!. ( 3est Cases
c. $ 3est Cases
d. :ot achieva!le
*'. Acceptance test cases are !ased on "hat9
a. Be-uirements
!. Design
c. Code
d. Decision ta!le
*+. LEo" much testing is enough9M
a. 3his -uestion is impossi!le to ans"er
!. 3his -uestion is easy to ans"er
c. 3he ans"er depends on the ris1 for your industry/ contract and special
re-uirements
d. 3his ans"er depends on the maturity of your developers
*<. A common test techni-ue during component test is
a. Statement and !ranch testing
!. .sa!ility testing
c. Security testing
d. Performance testing
*,. Statement Coverage "ill not chec1 for the follo"ing.
a. Missing Statements
!. .nused Branches
c. Dead Code
d. .nused Statement
*=. 5ndependent >erification G >alidation is
a. Done !y the Developer
!. Done !y the 3est Engineers
c. Done By Management
d. Done !y an Entity ;utside the Pro2ect0s sphere of influence
)%. Code Coverage is used as a measure of "hat 9
a. Defects
!. 3rends analysis
c. 3est Effectiveness
d. 3ime Spent 3esting
Ans"ers
* c
) d
( c
$ !
' c
+ !
< !
, c
= a
*% d
** c
*) !
*( !
*$ a
*' a
*+ c
*< a
*, a
*= d
)% c
* 8e split testing into distinct stages primarily !ecauseF
aA Each test stage has a different purpose.
!A 5t is easier to manage testing in stages.
cA 8e can run different tests in different environments.
dA 3he more stages "e have/ the !etter the testing.
) 8hich of the follo"ing is li1ely to !enefit most from the use of test tools providing test
capture and replay facilities9
aA Begression testing
!A 5ntegration testing
cA System testing
dA .ser acceptance testing
( 8hich of the follo"ing statements is :;3 correct9
aA A minimal test set that achieves *%%6 ?CSAH coverage "ill also achieve *%%6 !ranch
coverage.
!A A minimal test set that achieves *%%6 path coverage "ill also achieve *%%6 statement
coverage.
cA A minimal test set that achieves *%%6 path coverage "ill generally detect more faults
than one that achieves *%%6 statement coverage.
dA A minimal test set that achieves *%%6 statement coverage "ill generally detect more
faults than one that achieves *%%6 !ranch coverage.
$ 8hich of the follo"ing re-uirements is testa!le9
aA 3he system shall !e user friendly.
!A 3he safetycritical parts of the system shall contain % faults.
cA 3he response time shall !e less than one second for the specified design load.
dA 3he system shall !e !uilt to !e porta!le.
' Analyse the follo"ing highly simplified procedureF
As1F L8hat type of tic1et do you re-uire/ single or return9M
57 the customer "ants Nreturn0
As1F L8hat rate/ Standard or Cheapday9M
57 the customer replies NCheapday0
SayF L3hat "ill !e #**F)%M
E?SE
SayF L3hat "ill !e #*=F'%M
E:D57
E?SE
SayF L3hat "ill !e #=F<'M
E:D57
:o" decide the minimum num!er of tests that are needed to ensure that all
the -uestions have !een as1ed/ all com!inations have occurred and all
replies given.
aA (
!A $
cA 'dA +
+ Error guessingF
aA supplements formal test design techni-ues.
!A can only !e used in component/ integration and system testing.
cA is only performed in user acceptance testing.
dA is not repeata!le and should not !e used.
< 8hich of the follo"ing is :;3 true of test coverage criteria9
aA 3est coverage criteria can !e measured in terms of items exercised !y a test suite.
!A A measure of test coverage criteria is the percentage of user re-uirements covered.
cA A measure of test coverage criteria is the percentage of faults found.
dA 3est coverage criteria are often used "hen specifying test completion criteria.
, 5n prioritising "hat to test/ the most important o!2ective is toF
aA find as many faults as possi!le.
!A test high ris1 areas.
cA o!tain good test coverage.
dA test "hatever is easiest to test.
= Diven the follo"ing sets of test management terms @vzA/ and activity descriptions @*'A/
"hich one of the follo"ing !est pairs the t"o sets9
v 4 test control
" 4 test monitoring
x test estimation
y incident management
z configuration control
* calculation of re-uired test resources
) maintenance of record of test results
( reallocation of resources "hen tests overrun
$ report on deviation from test plan
' trac1ing of anomalous test results
aA v(/")/x*/y'/z$
!A v)/"'/x*/y$/z(
cA v(/"$/x*/y'/z)
dA v)/"*/x$/y(/z'
*% 8hich one of the follo"ing statements a!out system testing is :;3 true9
aA System tests are often performed !y independent teams.
!A 7unctional testing is used more than structural testing.
cA 7aults found during system tests can !e very expensive to fix.
dA Endusers should !e involved in system tests.
** 8hich of the follo"ing is false9
aA 5ncidents should al"ays !e fixed.
!A An incident occurs "hen expected and actual results differ.
cA 5ncidents can !e analysed to assist in test process improvement.
dA An incident can !e raised against documentation.
*) Enough testing has !een performed "henF
aA time runs out.
!A the re-uired level of confidence has !een achieved.
cA no more faults are found.
dA the users "on0t find any serious faults.
*( 8hich of the follo"ing is :;3 true of incidents9
aA 5ncident resolution is the responsi!ility of the author of the soft"are under test.
!A 5ncidents may !e raised against user re-uirements.
cA 5ncidents re-uire investigation andIor correction.
dA 5ncidents are raised "hen expected and actual results differ.
*$ 8hich of the follo"ing is not descri!ed in a unit test standard9
aA syntax testing
!A e-uivalence partitioning
cA stress testing
dA modified conditionIdecision coverage
*' 8hich of the follo"ing is false9
aA 5n a system t"o different failures may have different severities.
!A A system is necessarily more relia!le after de!ugging for the removal of a fault.
cA A fault need not affect the relia!ility of a system.
dA .ndetected errors may lead to faults and eventually to incorrect !ehaviour.
*+ 8hich one of the follo"ing statements/ a!out capturereplay tools/ is :;3 correct9
aA 3hey are used to support multiuser testing.
!A 3hey are used to capture and animate user re-uirements.
cA 3hey are the most fre-uently purchased types of CAS3 tool.
dA 3hey capture aspects of user !ehaviour.
*< Eo" "ould you estimate the amount of retesting li1ely to !e re-uired9
aA Metrics from previous similar pro2ects
!A Discussions "ith the development team
cA 3ime allocated for regression testing
dA a G !
*, 8hich of the follo"ing is true of the >model9
aA 5t states that modules are tested against user re-uirements.
!A 5t only models the testing phase.
cA 5t specifies the test techni-ues to !e used.
dA 5t includes the verification of designs.
*= 3he oracle assumptionF
aA is that there is some existing system against "hich test output may !e chec1ed.
!A is that the tester can routinely identify the correct outcome of a test.
cA is that the tester 1no"s everything a!out the soft"are under test.
dA is that the tests are revie"ed !y experienced testers.
)% 8hich of the follo"ing characterises the cost of faults9
aA 3hey are cheapest to find in the early development phases and the most expensive to fix
in the latest test phases.
!A 3hey are easiest to find during system testing !ut the most expensive to fix then.
cA 7aults are cheapest to find in the early development phases !ut the most expensive to fix
then.
dA Although faults are most expensive to find during early development phases/ they are
cheapest to fix then.
)* 8hich of the follo"ing should :;3 normally !e an o!2ective for a test9
aA 3o find faults in the soft"are.
!A 3o assess "hether the soft"are is ready for release.
cA 3o demonstrate that the soft"are doesn0t "or1.
dA 3o prove that the soft"are is correct.
)) 8hich of the follo"ing is a form of functional testing9
aA Boundary value analysis
!A .sa!ility testing
cA Performance testing
dA Security testing
)( 8hich of the follo"ing "ould :;3 normally form part of a test plan9
aA 7eatures to !e tested
!A 5ncident reports
cA Bis1s
dA Schedule
)$ 8hich of these activities provides the !iggest potential cost saving from the use of
CAS39
aA 3est management
!A 3est design
cA 3est execution
dA 3est planning
)' 8hich of the follo"ing is :;3 a "hite !ox techni-ue9
aA Statement testing
!A Path testing
cA Data flo" testing
dA State transition testing
)+ Data flo" analysis studiesF
aA possi!le communications !ottlenec1s in a program.
!A the rate of change of data values as a program executes.
cA the use of data on paths through the code.
dA the intrinsic complexity of the code.
)< 5n a system designed to "or1 out the tax to !e paidF
An employee has #$%%% of salary tax free. 3he next #*'%% is taxed at *%6
3he next #),%%% is taxed at ))6
Any further amount is taxed at $%6
3o the nearest "hole pound/ "hich of these is a valid Boundary >alue Analysis test case9
aA #*'%%
!A #()%%*
cA #(('%*
dA #),%%%
), An important !enefit of code inspections is that theyF
aA ena!le the code to !e tested !efore the execution environment is ready.
!A can !e performed !y the person "ho "rote the code.
cA can !e performed !y inexperienced staff.
dA are cheap to perform.
)= 8hich of the follo"ing is the !est source of Expected ;utcomes for .ser Acceptance 3est
scripts9
aA Actual results
!A Program specification
cA .ser re-uirements
dA System specification
(% 8hat is the main difference !et"een a "al1through and an inspection9
aA An inspection is lead !y the author/ "hilst a "al1through is lead !y a trained moderator.
!A An inspection has a trained leader/ "hilst a "al1through has no leader.
cA Authors are not present during inspections/ "hilst they are during "al1throughs.
dA A "al1through is lead !y the author/ "hilst an inspection is lead !y a trained moderator.
(* 8hich one of the follo"ing descri!es the ma2or !enefit of verification early in the life
cycle9
aA 5t allo"s the identification of changes in user re-uirements.
!A 5t facilitates timely set up of the test environment.
cA 5t reduces defect multiplication.
dA 5t allo"s testers to !ecome involved early in the pro2ect.
() 5ntegration testing in the smallF
aA tests the individual components that have !een developed.
!A tests interactions !et"een modules or su!systems.
cA only uses components that form part of the live system.
dA tests interfaces to other systems.
(( Static analysis is !est descri!ed asF
aA the analysis of !atch programs.
!A the revie"ing of test plans.
cA the analysis of program code.
dA the use of !lac1 !ox testing.
($ Alpha testing isF
aA postrelease testing !y end user representatives at the developer0s site.
!A the first testing that is performed.
cA prerelease testing !y end user representatives at the developer0s site.
dA prerelease testing !y end user representatives at their sites.
(' A failure isF
aA found in the soft"are& the result of an error.
!A departure from specified !ehaviour.
cA an incorrect step/ process or data definition in a computer program.
dA a human action that produces an incorrect result.
(+ 5n a system designed to "or1 out the tax to !e paidF
An employee has #$%%% of salary tax free. 3he next #*'%% is taxed at *%6
3he next #),%%% is taxed at ))6
Any further amount is taxed at $%6
8hich of these groups of num!ers "ould fall into the same e-uivalence class9
aA #$,%%& #*$%%%& #),%%%
!A #')%%& #''%%& #),%%%
cA #),%%*& #()%%%& #('%%%
dA #',%%& #),%%%& #()%%%
(< 3he most important thing a!out early test design is that itF
aA ma1es test preparation easier.
!A means inspections are not re-uired.
cA can prevent fault multiplication.
dA "ill find all faults.
(, 8hich of the follo"ing statements a!out revie"s is true9
aA Bevie"s cannot !e performed on user re-uirements specifications.
!A Bevie"s are the least effective "ay of testing code.
cA Bevie"s are unli1ely to find faults in test plans.
dA Bevie"s should !e performed on specifications/ code/ and test plans.
(= 3est cases are designed duringF
aA test recording.
!A test planning.
cA test configuration.
dA test specification.
$% A configuration management system "ould :;3 normally provideF
aA lin1age of customer re-uirements to version num!ers.
!A facilities to compare test results "ith expected results.
cA the precise differences in versions of soft"are component source code.
dA restricted access to the source code li!rary.
* A
) A
( D
$ C
' A
+ A
< C
, B
= C
*% D
** A
*) B
*( A
*$ C
*' B
*+ B
*< D
*, D
*= B
)% A
)* D
)) A
)( B
)$ C
)' D
)+ C
)< C
), A
)= C
(% D
(* C
() B
(( C
($ C
(' B
(+ D
(< C
(, D
(= D
$% B
*.Soft"are testing activities should start
a. as soon as the code is "ritten
!. during the design stage
c. "hen the re-uirements have !een formally documented
d. as soon as possi!le in the development life cycle
).7aults found !y users are due toF
a. Poor -uality soft"are
!. Poor soft"are and poor testing
c. !ad luc1
d. insufficient time for testing
(.8hat is the main reason for testing soft"are !efore releasing it9
a. to sho" that system "ill "or1 after release
!. to decide "hen the soft"are is of sufficient -uality to release
c. to find as many !ugs as possi!le !efore release
d. to give information for a ris1 !ased decision a!out release
$. "hich of the follo"ing statements is not true
a. performance testing can !e done during unit testing as "ell as during the testing of "hole
system
!. 3he acceptance test does not necessarily include a regression test
c. >erification activities should not involve testers @revie"s/ inspections etcA
d. 3est environments should !e as similar to production environments as possi!le
'. 8hen reporting faults found to developers/ testers should !eF
a. as polite/ constructive and helpful as possi!le
!. firm a!out insisting that a !ug is not a LfeatureM if it should !e fixed
c. diplomatic/ sensitive to the "ay they may react to criticism
d. All of the a!ove
+.5n "hich order should tests !e run9
a. the most important tests first
!. the most difficult tests first@to allo" maximum time for fixingA
c. the easiest tests first@to give initial confidenceA
d. the order they are thought of
<. 3he later in the development life cycle a fault is discovered/ the more expensive it is to
fix. "hy9
a. the documentation is poor/ so it ta1es longer to find out "hat the soft"are is doing.
!. "ages are rising
c. the fault has !een !uilt into more documentation/code/tests/ etc
d. none of the a!ove
,. 8hich is not true3he !lac1 !ox tester
a. should !e a!le to understand a functional specification or re-uirements document
!. should !e a!le to understand the source code.
c. is highly motivated to find faults
d. is creative to find the system0s "ea1nesses
=. A test design techni-ue is
a. a process for selecting test cases
!. a process for determining expected outputs
c. a "ay to measure the -uality of soft"are
d. a "ay to measure in a test plan "hat has to !e done
*%. 3est"are@test cases/ test datasetA
a. needs configuration management 2ust li1e re-uirements/ design and code
!. should !e ne"ly constructed for each ne" version of the soft"are
c. is needed only until the soft"are is released into production or use
d. does not need to !e documented and commented/ as it does not form part of the
released
soft"are system
**. An incident logging system
a only records defects
! is of limited value
c is a valua!le source of pro2ect information during testing if it contains all incidents
d. should !e used only !y the test team.
*). 5ncreasing the -uality of the soft"are/ !y !etter development methods/ "ill affect the
time needed for testing @the test phasesA !yF
a. reducing test time
!. no change
c. increasing test time
d. can0t say
*(. Coverage measurement
a. is nothing to do "ith testing
!. is a partial measure of test thoroughness
c. !ranch coverage should !e mandatory for all soft"are
d. can only !e applied at unit or module testing/ not at system testing
*$. 8hen should you stop testing9
a. "hen time for testing has run out.
!. "hen all planned tests have !een run
c. "hen the test completion criteria have !een met
d. "hen no faults have !een found !y the tests run
*'. 8hich of the follo"ing is true9
a. Component testing should !e !lac1 !ox/ system testing should !e "hite !ox.
!. if u find a lot of !ugs in testing/ you should not !e very confident a!out the -uality of
soft"are
c. the fe"er !ugs you find/the !etter your testing "as
d. the more tests you run/ the more !ugs you "ill find.
*+. 8hat is the important criterion in deciding "hat testing techni-ue to use9
a. ho" "ell you 1no" a particular techni-ue
!. the o!2ective of the test
c. ho" appropriate the techni-ue is for testing the application
d. "hether there is a tool to support the techni-ue
*<. 5f the pseudocode !elo" "ere a programming language /ho" many tests are re-uired to
achieve *%%6 statement coverage9
*. 5f xV( then
). DisplayPmessageO&
(. 5f yV) then
$. DisplayPmessageK&
'. Else
+. DisplayPmessageS&
<. Else
,. DisplayPmessageS&
a. *
!. )
c. (
d. $
*,. .sing the same code example as -uestion *</ho" many tests are re-uired to achieve
*%%6 !ranchIdecision coverage9
a. *
!. )
c. (
d. $
*= 8hich of the follo"ing is :;3 a type of nonfunctional test9
a. State3ransition
!. .sa!ility
c. Performance
d. Security
)%. 8hich of the follo"ing tools "ould you use to detect a memory lea19
a. State analysis
!. Coverage analysis
c. Dynamic analysis
d. Memory analysis
)*. 8hich of the follo"ing is :;3 a standard related to testing9
a. 5EEE,)=
!. 5EEE+*%
c. BS<=)'*
d. BS<=)')
))."hich of the follo"ing is the component test standard9
a. 5EEE ,)=
!. 5EEE +*%
c. BS<=)'*
d. BS<=)')
)( "hich of the follo"ing statements are true9
a. 7aults in program specifications are the most expensive to fix.
!. 7aults in code are the most expensive to fix.
c. 7aults in re-uirements are the most expensive to fix
d. 7aults in designs are the most expensive to fix.
)$. 8hich of the follo"ing is not the integration strategy9
a. Design !ased
!. Big!ang
c. Bottomup
d. 3opdo"n
)'. 8hich of the follo"ing is a !lac1 !ox design techni-ue9
a. statement testing
!. e-uivalence partitioning
c. error guessing
d. usa!ility testing
)+. A program "ith high cyclometic complexity is almost li1ely to !eF
a. ?arge
!. Small
c. Difficult to "rite
d. Difficult to test
)<. 8hich of the follo"ing is a static test9
a. code inspection
!. coverage analysis
c. usa!ility assessment
d. installation test
),. 8hich of the follo"ing is the odd one out9
a. "hite !ox
!. glass !ox
c. structural
d. functional
)=. A program validates a numeric field as follo"sF
values less than *% are re2ected/ values !et"een *% and )* are accepted/ values greater
than or e-ual to )) are re2ected
"hich of the follo"ing input values cover all of the e-uivalence partitions9
a. *%/**/)*
!. (/)%/)*
c. (/*%/))
d. *%/)*/))
(%. .sing the same specifications as -uestion )=/ "hich of the follo"ing covers the M;S3
!oundary values9
a. =/*%/**/))
!. =/*%/)*/))
c. *%/**/)*/))
d. *%/**/)%/)*
*.d
).!
(.d
$.c
'.d
+.a
<.c
,.!
=.a
*%.a
**.c
*).a
*(.!
*$.c
*'.!
*+.!
*<.c
*,.c
*=.a
)%.c
)*.!
)).d
)(.c
)$.a
)'.!
)+.d
)<.a
),.d
)=.c
(%.!
* 8hen "hat is visi!le to endusers is a deviation from the specific or expected !ehavior/
this is calledF
aA an error
!A a fault
cA a failure
dA a defect
eA a mista1e
) Begression testing should !e performedF
vA every "ee1
"A after the soft"are has changed
xA as often as possi!le
yA "hen the environment has changed
zA "hen the pro2ect manager says
aA v G " are true/ x 4 z are false
!A "/ x G y are true/ v G z are false
cA " G y are true/ v/ x G z are false
dA " is true/ v/ x y and z are false
eA all of the a!ove are true
( 5EEE ,)= test plan documentation standard contains all of the follo"ing exceptF
aA test items
!A test delivera!les
cA test tas1s
dA test environment
eA test specification
$ 3esting should !e stopped "henF
aA all the planned tests have !een run
!A time has run out
cA all faults have !een fixed correctly
dA !oth aA and cA
eA it depends on the ris1s for the system !eing tested
' ;rder num!ers on a stoc1 control system can range !et"een *%%%% and ===== inclusive.
8hich of the follo"ing inputs might !e a result of designing tests for only valid e-uivalence
classes and valid !oundariesF
aA *%%%/ '%%%/ =====
!A ====/ '%%%%/ *%%%%%
cA *%%%%/ '%%%%/ =====
dA *%%%%/ =====
eA ====/ *%%%%/ '%%%%/ =====/ *%%%%
+ Consider the follo"ing statements a!out early test designF
i. early test design can prevent fault multiplication
ii. faults found during early test design are more expensive to fix
iii. early test design can find faults
iv. early test design can cause changes to the re-uirements
v. early test design ta1es more effort
aA i/ iii G iv are true. 5i G v are false
!A iii is true/ 5/ ii/ iv G v are false
cA iii G iv are true. i/ ii G v are false
dA i/ iii/ iv G v are true/ ii us false
eA i G iii are true/ ii/ iv G v are false
< :onfunctional system testing includesF
aA testing to see "here the system does not function properly
!A testing -uality attri!utes of the system including performance and usa!ility
cA testing a system feature using only the soft"are re-uired for that action
dA testing a system feature using only the soft"are re-uired for that function
eA testing for functions that should not exist
, 8hich of the follo"ing is :;3 part of configuration managementF
aA status accounting of configuration items
!A auditing conformance to 5S;=%%*
cA identification of test versions
dA record of changes to documentation over time
eA controlled li!rary access
= 8hich of the follo"ing is the main purpose of the integration strategy for integration
testing in the small9
aA to ensure that all of the small modules are tested ade-uately
!A to ensure that the system interfaces to other systems and net"or1s
cA to specify "hich modules to com!ine "hen and ho" many at once
dA to ensure that the integration testing can !e performed !y a small team
eA to specify ho" the soft"are should !e divided into modules
*% 8hat is the purpose of test completion criteria in a test planF
aA to 1no" "hen a specific test has finished its execution
!A to ensure that the test case specification is complete
cA to set the criteria used in generating test inputs
dA to 1no" "hen test planning is complete
eA to plan "hen to stop testing
** Consider the follo"ing statements
i. an incident may !e closed "ithout !eing fixed
ii. incidents may not !e raised against documentation
iii. the final stage of incident trac1ing is fixing
iv. the incident record does not include information on test environments
v. incidents should !e raised "hen someone other than the author of the soft"are performs
the test
aA ii and v are true/ 5/ iii and iv are false
!A i and v are true/ ii/ iii and iv are false
cA i/ iv and v are true/ ii and iii are false
dA i and ii are true/ iii/ iv and v are false
eA i is true/ ii/ iii/ iv and v are false
*) Diven the follo"ing code/ "hich is true a!out the minimum num!er of test cases
re-uired for full statement and !ranch coverageF
Bead P
Bead C
57 PRC U *%% 3EE:
Print L?argeM
E:D57
5f P U '% 3EE:
Print LP ?argeM
E:D57
aA * test for statement coverage/ ( for !ranch coverage
!A * test for statement coverage/ ) for !ranch coverage
cA * test for statement coverage/ * for !ranch coverage
dA ) tests for statement coverage/ ( for !ranch coverage
eA ) tests for statement coverage/ ) for !ranch coverage
*( Diven the follo"ingF
S"itch PC on
Start Loutloo1M
57 outloo1 appears 3EE:
Send an email
Close outloo1
aA * test for statement coverage/ * for !ranch coverage
!A * test for statement coverage/ ) for !ranch coverage
cA * test for statement coverage. ( for !ranch coverage
dA ) tests for statement coverage/ ) for !ranch coverage
eA ) tests for statement coverage/ ( for !ranch coverage
*$ Diven the follo"ing code/ "hich is trueF
57 A U B 3EE:
C V A 4 B
E?SE
C V A R B
E:D57
Bead D
57 C V D 3hen
Print LErrorM
E:D57
aA * test for statement coverage/ ( for !ranch coverage
!A ) tests for statement coverage/ ) for !ranch coverage
cA ) tests for statement coverage. ( for !ranch coverage
dA ( tests for statement coverage/ ( for !ranch coverage
eA ( tests for statement coverage/ ) for !ranch coverage
*' Consider the follo"ingF
Pic1 up and read the ne"spaper
?oo1 at "hat is on television
5f there is a program that you are interested in "atching then s"itch the the television on
and "atch the program
;ther"ise
Continue reading the ne"spaper
5f there is a cross"ord in the ne"spaper then try and complete the cross"ord
aA SC V * and DC V *
!A SC V * and DC V )
cA SC V * and DC V (
dA SC V ) and DC V )
eA SC V ) and DC V (
*+ 3he place to start if you "ant a @ne"A test tool isF
aA Attend a tool exhi!ition
!A 5nvite a vendor to give a demo
cA Analyse your needs and re-uirements
dA 7ind out "hat your !udget "ould !e for the tool
eA Search the internet
*< 8hen a ne" testing tool is purchased/ it should !e used first !yF
aA A small team to esta!lish the !est "ay to use the tool
!A Everyone "ho may eventually have some use for the tool
cA 3he independent testing team
dA 3he managers to see "hat pro2ects it should !e used in
eA 3he vendor contractor to "rite the initial scripts
*, 8hat can static analysis :;3 find9
aA 3he use of a varia!le !efore it has !een defined
!A .nreacha!le @LdeadMA code
cA 8hether the value stored in a varia!le is correct
dA 3he redefinition of a varia!le !efore it has !een used
eA Array !ound violations
*= 8hich of the follo"ing is :;3 a !lac1 !ox techni-ueF
aA E-uivalence partitioning
!A State transition testing
cA ?CSAH
dA Syntax testing
eA Boundary value analysis
)% Beta testing isF
aA Performed !y customers at their o"n site
!A Performed !y customers at their soft"are developer0s site
cA Performed !y an independent test team
dA .seful to test !espo1e soft"are
eA Performed as early as possi!le in the lifecycle
)* Diven the follo"ing types of tool/ "hich tools "ould typically !e used !y developers and
"hich !y an independent test teamF
i. static analysis
ii. performance testing
iii. test management
iv. dynamic analysis
v. test running
vi. test data preparation
aA developers "ould typically use i/ iv and vi& test team ii/ iii and v
!A developers "ould typically use i and iv& test team ii/ iii/ v and vi
cA developers "ould typically use i/ ii/ iii and iv& test team v and vi
dA developers "ould typically use ii/ iv and vi& test team 5/ ii and v
eA developers "ould typically use i/ iii/ iv and v& test team ii and vi
)) 3he main focus of acceptance testing isF
aA finding faults in the system
!A ensuring that the system is accepta!le to all users
cA testing the system "ith other systems
dA testing for a !usiness perspective
eA testing !y an independent test team
)( 8hich of the follo"ing statements a!out the component testing standard is falseF
aA !lac1 !ox design techni-ues all have an associated measurement techni-ue
!A "hite !ox design techni-ues all have an associated measurement techni-ue
cA cyclomatic complexity is not a test measurement techni-ue
dA !lac1 !ox measurement techni-ues all have an associated test design techni-ue
eA "hite !ox measurement techni-ues all have an associated test design techni-ue
)$ 8hich of the follo"ing statements is :;3 trueF
aA inspection is the most formal revie" process
!A inspections should !e led !y a trained leader
cA managers can perform inspections on management documents
dA inspection is appropriate even "hen there are no "ritten documents
eA inspection compares documents "ith predecessor @sourceA documents
)' A typical commercial test execution tool "ould !e a!le to perform all of the follo"ing
EOCEP3F
aA generating expected outputs
!A replaying inputs according to a programmed script
cA comparison of expected outcomes "ith actual outcomes
dA recording test inputs
eA reading test values from a data file
)+ 3he difference !et"een retesting and regression testing is
aA retesting is running a test again& regression testing loo1s for unexpected side effects
!A retesting loo1s for unexpected side effects& regression testing is repeating those tests
cA retesting is done after faults are fixed& regression testing is done earlier
dA retesting uses different environments/ regression testing uses the same environment
eA retesting is done !y developers/ regression testing is done !y independent testers
)< Expected results areF
aA only important in system testing
!A only used in component testing
cA never specified in advance
dA most useful "hen specified in advance
eA derived from the code
), 3est managers should notF
aA report on deviations from the pro2ect plan
!A sign the system off for release
cA reallocate resource to meet original plans
dA raise incidents on faults that they have found
eA provide information for ris1 analysis and -uality improvement
)= .nreacha!le code "ould !est !e found usingF
aA code revie"s
!A code inspections
cA a coverage tool
dA a test management tool
eA a static analysis tool
(% A tool that supports tracea!ility/ recording of incidents or scheduling of tests is calledF
aA a dynamic analysis tool
!A a test execution tool
cA a de!ugging tool
dA a test management tool
eA a configuration management tool
(* 8hat information need not !e included in a test incident reportF
aA ho" to fix the fault
!A ho" to reproduce the fault
cA test environment details
dA severity/ priority
eA the actual and expected outcomes
() 8hich expression !est matches the follo"ing characteristics or revie" processesF
*. led !y author
). undocumented
(. no management participation
$. led !y a trained moderator or leader
'. uses entry exit criteria
sA inspection
tA peer revie"
uA informal revie"
vA "al1through
aA s V $/ t V (/ u V ) and '/ v V *
!A s V $ and '/ t V (/ u V )/ v V *
cA s V * and '/ t V (/ u V )/ v V $
dA s V '/ t V $/ u V (/ v V * and )
eA s V $ and '/ t V */ u V )/ v V (
(( 8hich of the follo"ing is :;3 part of system testingF
aA !usiness process!ased testing
!A performance/ load and stress testing
cA re-uirements!ased testing
dA usa!ility testing
eA topdo"n integration testing
($ 8hat statement a!out expected outcomes is 7A?SEF
aA expected outcomes are defined !y the soft"are0s !ehaviour
!A expected outcomes are derived from a specification/ not from the code
cA expected outcomes include outputs to a screen and changes to files and data!ases
dA expected outcomes should !e predicted !efore a test is run
eA expected outcomes may include timing constraints such as response times
(' 3he standard that gives definitions of testing terms isF
aA 5S;I5EC *))%<
!A BS<=)'*
cA BS<=)')
dA A:S5I5EEE ,)=
eA A:S5I5EEE <)=
(+ 3he cost of fixing a faultF
aA 5s not important
!A 5ncreases as "e move the product to"ards live use
cA Decreases as "e move the product to"ards live use
dA 5s more expensive if found in re-uirements than functional design
eA Can never !e determined
(< 8hich of the follo"ing is :;3 included in the 3est Plan document of the 3est
Documentation StandardF
aA 3est items @i.e. soft"are versionsA
!A 8hat is not to !e tested
cA 3est environments
dA Cuality plans
eA Schedules and deadlines
(, Could revie"s or inspections !e considered part of testingF
aA :o/ !ecause they apply to development documentation
!A :o/ !ecause they are normally applied !efore testing
cA :o/ !ecause they do not apply to the test documentation
dA Kes/ !ecause !oth help detect faults and improve -uality
eA Kes/ !ecause testing includes all nonconstructive activities
(= 8hich of the follo"ing is not part of performance testingF
aA Measuring response time
!A Measuring transaction rates
cA Becovery testing
dA Simulating many users
eA Denerating many transactions
$% Error guessing is !est used
aA As the first approach to deriving test cases
!A After more formal techni-ues have !een applied
cA By inexperienced testers
dA After the system has gone live
eA ;nly !y end users
Cuestion num!er Correct ans"er
* C
) C
( E
$ E
' C
+ A
< B
, B
= C
*% E
** B
*) B
*( B
*$ B
*' E
*+ C
*< B
*, C
*= C
)% A
)* B
)) D
)( A
)$ D
)' A
)+ A
)< D
), C
)= A
(% E
(* E
() B
(( E
($ A
(' B
(+ B
(< D
(, D
(= C
$% B