NEW
Font size
WorksheetsCTFL MOCK QUIZ - 02
Total questions: 40
Worksheet time: 20mins
When what is visible to end-users is a deviation from the specific or expected behavior, this is
called:
an error
a fault
a failure
a defect
a mistake
Regression testing should be performed:
v) every week
w) after the software has changed
x) as often as possible
y) when the environment has changed
z) when the project manager says
v & w are true, x – z are false
w, x & y are true, v & z are false
w & y are true, v, x & z are false
w is true, v, x y and z are false
all of the above are true
IEEE 829 test plan documentation standard contains all of the following except:
test items
test deliverables
test tasks
test environment
test specification
Testing should be stopped when:
all the planned tests have been run
time has run out
all faults have been fixed correctly
both a) and c)
it depends on the risks for the system being tested
Order numbers on a stock control system can range between 10000 and 99999 inclusive. Which of the following inputs might be a result of designing tests for only valid equivalence classes and valid boundaries:
1000, 5000, 99999
9999, 50000, 100000
10000, 50000, 99999
10000, 99999
9999, 10000, 50000, 99999, 10000
Consider the following statements about early test design:
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 requirements
v. early test design takes more effort
i, iii & iv are true. ii & v are false
iii is true, i, ii, iv & v are false
iii & iv are true. i, ii & v are false
i, iii, iv & v are true, ii us false
i & iii are true, ii, iv & v are false
Non-functional system testing includes:
testing to see where the system does not function properly
testing quality attributes of the system including performance and usability
testing a system feature using only the software required for that action
testing a system feature using only the software required for that function
testing for functions that should not exist
Which of the following is NOT part of configuration management:
status accounting of configuration items
auditing conformance to ISO9001
identification of test versions
record of changes to documentation over time
controlled library access
Which of the following is the main purpose of the integration strategy for integration testing in the small?
to ensure that all of the small modules are tested adequately
to ensure that the system interfaces to other systems and networks
to specify which modules to combine when and how many at once
to ensure that the integration testing can be performed by a small team
to specify how the software should be divided into modules
What is the purpose of test completion criteria in a test plan:
to know when a specific test has finished its execution
to ensure that the test case specification is complete
to set the criteria used in generating test inputs
to know when test planning is complete
to plan when to stop testing
Consider the following statements
i. an incident may be closed without being fixed
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
v. incidents should be raised when someone other than the author of the software performs the test
ii and v are true, i, iii and iv are false
i and v are true, ii, iii and iv are false
i, iv and v are true, ii and iii are false
i and ii are true, iii, iv and v are false
i is true, ii, iii, iv and v are false
Given the following code, which is true about the minimum number of test cases required for full statement and branch coverage:
Read P
Read Q
IF P+Q > 100 THEN
Print “Large”
ENDIF
If P > 50 THEN
Print “P Large”
ENDIF
1 test for statement coverage, 3 for branch coverage
1 test for statement coverage, 2 for branch coverage
1 test for statement coverage, 1 for branch coverage
2 tests for statement coverage, 3 for branch coverage
2 tests for statement coverage, 2 for branch coverage
Given the following:
Switch PC on
Start “outlook”
IF outlook appears THEN
Send an email
Close outlook
1 test for statement coverage, 1 for branch coverage
1 test for statement coverage, 2 for branch coverage
1 test for statement coverage. 3 for branch coverage
2 tests for statement coverage, 2 for branch coverage
2 tests for statement coverage, 3 for branch coverage
Given the following code, which is true:
IF A > B THEN
C = A – B
ELSE
C = A + B
ENDIF
Read D
IF C = D Then
Print “Error”
ENDIF
1 test for statement coverage, 3 for branch coverage
2 tests for statement coverage, 2 for branch coverage
2 tests for statement coverage. 3 for branch coverage
3 tests for statement coverage, 3 for branch coverage
3 tests for statement coverage, 2 for branch coverage
Consider the following:
Pick up and read the newspaper
Look at what is on television
If there is a program that you are interested in watching then switch the television on and watch the program
Otherwise
Continue reading the newspaper
If there is a crossword in the newspaper then try and complete the crossword
SC = 1 and DC = 1
SC = 1 and DC = 2
SC = 1 and DC = 3
SC = 2 and DC = 2
SC = 2 and DC = 3
The place to start if you want a (new) test tool is:
Attend a tool exhibition
Invite a vendor to give a demo
Analyse your needs and requirements
Find out what your budget would be for the tool
Search the internet
When a new testing tool is purchased, it should be used first by:
A small team to establish the best way to use the tool
Everyone who may eventually have some use for the tool
The independent testing team
The managers to see what projects it should be used in
The vendor contractor to write the initial scripts
What can static analysis NOT find?
The use of a variable before it has been defined
Unreachable (“dead”) code
Whether the value stored in a variable is correct
The re-definition of a variable before it has been used
Array bound violations
Which of the following is NOT a black box technique:
Equivalence partitioning
State transition testing
LCSAJ
Syntax testing
Boundary value analysis
Beta testing is:
Performed by customers at their own site
Performed by customers at their software developer’s site
Performed by an independent test team
Useful to test bespoke software
Performed as early as possible in the lifecycle
Given the following types of tool, which tools would typically be used by developers and which by an independent test team:
i. static analysis
ii. performance testing
iii. test management
iv. dynamic analysis
v. test running
vi. test data preparation
developers would typically use i, iv and vi; test team ii, iii and v
developers would typically use i and iv; test team ii, iii, v and vi
developers would typically use i, ii, iii and iv; test team v and vi
developers would typically use ii, iv and vi; test team i, ii and v
developers would typically use i, iii, iv and v; test team ii and vi
The main focus of acceptance testing is:
finding faults in the system
ensuring that the system is acceptable to all users
testing the system with other systems
testing for a business perspective
testing by an independent test team
Which of the following statements about the component testing standard is false:
black box design techniques all have an associated measurement technique
white box design techniques all have an associated measurement technique
cyclomatic complexity is not a test measurement technique
black box measurement techniques all have an associated test design technique
white box measurement techniques all have an associated test design technique
Which of the following statements is NOT true:
inspection is the most formal review process
inspections should be led by a trained leader
managers can perform inspections on management documents
inspection is appropriate even when there are no written documents
inspection compares documents with predecessor (source) documents
A typical commercial test execution tool would be able to perform all of the following EXCEPT:
generating expected outputs
replaying inputs according to a programmed script
comparison of expected outcomes with actual outcomes
recording test inputs
reading test values from a data file
The difference between re-testing and regression testing is
re-testing is running a test again; regression testing looks for unexpected side effects
re-testing looks for unexpected side effects; regression testing is repeating those tests
re-testing is done after faults are fixed; regression testing is done earlier
re-testing uses different environments, regression testing uses the same environment
re-testing is done by developers, regression testing is done by independent testers
Expected results are:
only important in system testing
only used in component testing
never specified in advance
most useful when specified in advance
derived from the code
Test managers should not:
report on deviations from the project plan
sign the system off for release
re-allocate resource to meet original plans
raise incidents on faults that they have found
provide information for risk analysis and quality improvement
Unreachable code would best be found using:
code reviews
code inspections
a coverage tool
a test management tool
a static analysis tool
A tool that supports traceability, recording of incidents or scheduling of tests is called:
a dynamic analysis tool
a test execution tool
a debugging tool
a test management tool
a configuration management tool
What information need not be included in a test incident report:
how to fix the fault
how to reproduce the fault
test environment details
severity, priority
the actual and expected outcomes
Which expression best matches the following characteristics or review processes:
1. led by author
2. undocumented
3. no management participation
4. led by a trained moderator or leader
5. uses entry exit criteria
s) inspection
t) peer review
u) informal review
v) walkthrough
s = 4, t = 3, u = 2 and 5, v = 1
s = 4 and 5, t = 3, u = 2, v = 1
s = 1 and 5, t = 3, u = 2, v = 4
s = 5, t = 4, u = 3, v = 1 and 2
s = 4 and 5, t = 1, u = 2, v = 3
Which of the following is NOT part of system testing:
business process-based testing
performance, load and stress testing
requirements-based testing
usability testing
top-down integration testing
What statement about expected outcomes is FALSE:
expected outcomes are defined by the software’s behaviour
expected outcomes are derived from a specification, not from the code
expected outcomes include outputs to a screen and changes to files and databases
expected outcomes should be predicted before a test is ru
expected outcomes may include timing constraints such as response times
The standard that gives definitions of testing terms is:
ISO/IEC 12207
BS7925-1
BS7925-2
ANSI/IEEE 829
ANSI/IEEE 729
The cost of fixing a fault:
Is not important
Increases as we move the product towards live use
Decreases as we move the product towards live use
Is more expensive if found in requirements than functional design
Can never be determined
Which of the following is NOT included in the Test Plan document of the Test Documentation Standard:
Test items (i.e. software versions)
What is not to be tested
Test environments
Quality plans
Schedules and deadlines
Could reviews or inspections be considered part of testing:
No, because they apply to development documentation
No, because they are normally applied before testing
No, because they do not apply to the test documentation
Yes, because both help detect faults and improve quality
Yes, because testing includes all non-constructive activities
Which of the following is not part of performance testing:
Measuring response time
Measuring transaction rates
Recovery testing
Simulating many users
Generating many transactions
Error guessing is best used
As the first approach to deriving test cases
After more formal techniques have been applied
By inexperienced testers
After the system has gone live
Only by end users
