b) a fault
c) a failure
d) a defect
w) after the software has changed
x) as often as possible
y) when the environment has changed
z) when the project manager says
b) w, x & y are true, v & z are false
c) w & y are true, v, x & z are false
d) w is true, v, x, y & z are false
b) test deliverables
c) test tasks
d) test specifications
b) when time has run out
c) when all faults have been fixed correctly
d) it depends on the risks for the system being tested
b) 9999, 50000, 100000
c) 10000, 50000, 99999
d) 10000, 99999, 100000
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 requirements
v. early test design normally takes more effort
b) iii & iv are true; i, ii & v are false
c) i, iii, iv & v are true; ii is false
d) i & ii are true; iii, iv & v are false
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 exist
b) status accounting of configuration items
c) identification of test versions
d) controlled library access
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
b) to ensure that the test case specification is complete
c) to set the criteria used in generating test inputs
d) to determine when to stop testing
ii. incidents may not be raised against documentation.
iii. the final stage of incident tracking is fixing.
iv. the incident record does not include information on test environments.
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
Read q
IF p+q > 100 THEN
Print “Large”
ENDIF
IF p > 50 THEN
Print “p Large”
ENDIF
b) 1 test for statement coverage, 2 for branch coverage
c) 1 test for statement coverage, 1 for branch coverage
d) 2 tests for statement coverage, 2 for branch coverage
ii. 100% branch coverage guarantees 100% statement coverage.
iii. 100% branch coverage guarantees 100% decision coverage.
iv. 100% decision coverage guarantees 100% branch coverage.
v. 100% statement coverage guarantees 100% decision coverage.
b) i & v are True; ii, iii & iv are False
c) ii & iii are True; i, iv & v are False
d) ii, iii & iv are True; i & v are False
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 specified response times
b) documentation
c) test cases
d) improvements suggested by users
b) test documentation
c) live data
d) user requirement documents
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
b) unreachable (“dead”) code
c) memory leaks
d) array bound violations
b) LCSAJ
c) syntax testing
d) boundary value analysis
b) performed by customers at the software developer’s site
c) performed by an Independent Test Team
d) performed as early as possible in the lifecycle
ii. performance testing
iii. test management
iv. dynamic analysis
b) developers would typically use i and iii; test team ii and iv
c) developers would typically use ii and iv; test team i and iii
d) developers would typically use i, iii and iv; test team ii
b) ensuring that the system is acceptable to all users
c) testing the system with other systems
d) testing from a business perspective
b) white box test design techniques all have an associated test measurement technique
c) cyclomatic complexity is not a test measurement technique
d) black box test measurement techniques all have an associated test design technique
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
b) comparison of expected outcomes with actual outcomes
c) recording test inputs
d) reading test values from a data file
b) re-testing looks for unexpected side-effects; regression testing ensures the original fault has been removed
c) re-testing is done after faults are fixed; regression testing is done earlier
d) re-testing is done by developers; regression testing is done by independent testers
b) only used in component testing
c) most useful when specified in advance
d) derived from the code
b) inspection
c) management review
d) post project review
b) non-functional system testing
c) user acceptance testing
d) maintenance testing
b) analyzing metrics and improving processes
c) writing the documents to be inspected
d) time spent on the document outside the meeting
b) to prove that the software has no faults
c) to give confidence in the software
d) to find performance problems
2. undocumented
3. no management participation
4. led by a moderator or leader
5. uses entry and exit criteria
t) peer review
u) informal review
v) walkthrough
b) s = 4, t = 3, u = 2 and 5, v = 1
c) s = 1 and 5, t = 3, u = 2, v = 4
d) s = 4 and 5, t = 1, u= 2, v = 3
b) performance, load and stress testing
c) usability testing
d) top-down integration testing
b) expected outcomes are derived from a specification, not from the code
c) expected outcomes should be predicted before a test is run
d) expected outcomes may include timing constraints such as response times
b) BS 7925-1
c) ANSI/IEEE 829
d) ANSI/IEEE 729
b) increases the later a fault is found
c) decreases the later a fault is found
d) can never be determined
b) test environment properties
c) quality plans
d) schedules and deadlines
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 non-constructive activities
b) recovery testing
c) simulating many users
d) generating many transactions
b) as the first approach to deriving test cases
c) by inexperienced testers
d) after the system has gone live
1 C
2 C
3 D
4 D
5 C
6 A
7 B
8 A
9 C
10 D
11 B
12 B
13 D
14 C
15 D
16 C
17 B
18 C
19 B
20 A
21 A
22 D
23 A
24 D
25 A
26 A
27 C
28 B
29 D
30 C
31 B
32 A
33 D
34 A
35 B
36 B
37 C
38 C
39 B
40 A










