Topic 21: Mix Questions Set A
What can a risk-based approach to testing provide?
A.
The types of test techniques to be employed.
B.
The total tests needed to provide 100 per cent coverage.
C.
An estimation of the total cost of testing.
D.
Only that test execution is effective at reducing risk
The types of test techniques to be employed.
Which of the following defines the expected result of a test?
A.
Test case
B.
Test procedure
C.
Test execution schedule
D.
Test condition
Test case
A software component has the code shown below:
Program BiggestA,
Biggest: Integer
Begin
Read A
Biggest = 10
While A > 0
Do
If A > Biggest
Then Biggest = A
EndifRead A
Enddo
End
The component has exit criteria for component testing that include 100% statement
coverage. Which of the following test cases will satisfy this criterion?
A.
0
B.
10, 0
C.
10, 5, 0
D.
10, 11, 0
10, 11, 0
Which of the following is most likely to cause failure in the implementation of a test tool?
A.
Underestimating the demand for a tool.
B.
The purchase price of the tool.
C.
No agreed requirements for the tool.
D.
The cost of resources to implement and maintain the tool.
No agreed requirements for the tool.
Important consequences of the impossibility of complete testing are:
A.
We can never be certain that the program is bug free.
B.
We have no definite stopping point for testing, which makes it easier for some managers
to argue for very little testing.
C.
We have no easy answer for what testing tasks should always be required, because
every task takes time that could be spent on other high importance tasks.
D.
All of the above
All of the above
Which of the following has the typical formal review activities in the correct sequence?
A.
Kick-off, review meeting, planning, follow-up.
B.
Kick-off, planning, review meeting, re-work.
C.
Planning, kick-off, individual preparation, review meeting.
D.
Planning, individual preparation, follow-up, re-work.
Planning, kick-off, individual preparation, review meeting.
The correct sequence is: planning, kick-off, individual preparation, review meeting, re-work,
follow-up. All of the other options have either the activities in the wrong order or activities
missing from the strict flow.
What if the project isn't big enough to justify extensive testing..?
A.
Use risk based analysis to find out which areas need to be tested
B.
Use automation tool for testing
C.
Both a and b
D.
None of the above
Use risk based analysis to find out which areas need to be tested
What do you mean by “Having to say NO”..?
A.
No, the problem is not with testers
B.
No, the software is not ready for production
C.
Both a & b
D.
None of the above
No, the software is not ready for production
What test roles (or parts in the testing process) is a developer most likely to perform?
(i) Executing component integration tests.
(ii) Static analysis.
(iii) Setting up the test environment.
(iv) Deciding how much testing should be automated.
A.
(i) and (ii)
B.
(i) and (iv)
C.
(ii) and (iii)
(i) and (ii)
(i) Executing component integration tests is usually done by developers. Developers are
usually responsible for unit and component integration testing. Independent testing usually
follows at system and acceptance test levels.
(ii) Static analysis is usually done by developers because: it requires an understanding of
the code and therefore the person doing this needs skills in the programming language;
and it can be done as soon as the code is written. Therefore it is quick and effective for the
developer to do it. The risk of a lack of test independence can be mitigated by performing
independent system and acceptance testing.
(iii) Setting up the test environment is an activity typically performed by a tester. It may
require support from developers and staff from other departments and on some occasions
environments could be set up by developers. However, it is a task that could be done by a
tester rather than a developer.
(iv) Deciding how much testing should be automated is typically a decision made by the
test leader, who will consult other staff in the decision-making process. Developers may be
involved and their skills may be required to automate some tests. However, the decision on
how much to automate should not be made by developers.
One Key reason why developers have difficulty testing their own work is:
A.
Lack of technical documentation
B.
Lack of test tools on the market for developers
C.
Lack of training
D.
Lack of Objectivity
Lack of training
| Page 10 out of 33 Pages |
| Previous |
Copyright © - All Rights Reserved