1. What is failure?
A. Deviation from expected result to actual result
B. Defect in the software.
C. Error in the program code.
D. Fault in the system.
2. Exclusive use of white box testing in a test-phase will:
A. Ensure the test item is adequately tested.
B. Make the need for black-box testing redundant.
C. Run the risk that the requirements are not satisfied.
D. Suffices for the unit testing phase.
3. Which of the following is least important in test management?
A. Estimating test duration.
B. Incident Management.
C. Configuration Management.
D. De-bugging.
4. A standard for software testing terminology is:
A. IEEE 802.11
B. ISO 9001
C. BS 7925-1
D. BS 7925-2
5. Which of the following is NOT a characteristic of User Acceptance Testing?
A. Use of automated test execution tools.
B. Testing performed by users.
C. Testing against acceptance test criteria.
D. Integration of system with user documentation.
6. Which of the following provides the biggest potential cost saving from use of CAST?
A. Test management
B. Test design
C. Test planning
D. Test execution
7. What type of testing is done to supplement the rigorous testing?
A. Regression testing.
B. Integration testing.
C. Error Guessing
D. System testing.
8. To make a test effective it is most important that:
A. It is easy to execute.
B. It is designed to detect faults if present.
C. The expected outcome is specified before execution.
D. It is unlikely to delay progress.
9. Error guessing is:
A. An appropriate way of deriving system tests.
B. Only used if good requirements are not available.
C. Only used when good requirements are available.
D. The most appropriate way of deriving system tests.
10. Amount of testing performed will not depend on
A. Risks involved
B. Contractual requirements
C. Legal requirements
D. Test data.
11. For software to be reliable it must:
A. Be easy to maintain.
B. Be unlikely to cause a failure.
C. Never fail under any circumstances.
D. Be written according to coding standards
12. In a system designed to work out the tax to be paid: An employee has $4000 of salary tax free. The next $1500 is taxed at 10% The next $28000 is taxed at 22% Any further amount is taxed at 40%
To the nearest $ which of these is a valid Boundary Value Analysis test case?
A. $1500
B. $32001
C. $28000
D. $33501
13. Faults found by users are due to:
A. Poor quality software
B. Poor software and poor testing
C. Bad luck
D. Insufficient time for testing
14. An incident logging system
A. Only records defects
B. Is of limited value
C. Is a valuable source of project information during testing if it contains all incidents
D. Should be used only by the test team.
15. The later in the development life cycle a fault is discovered, the more expensive it is to fix. Why?
A. The documentation is poor, so it takes longer to find 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
16. Which of the following is true?
A. Component testing should be black box, system testing should be white box.
B. If u find a lot of bugs in testing, you should not be very confident about the quality of software
C. The fewer bugs you find, the better your testing was
D. The more tests you run, the more bugs you will find.
17. If the pseudo code below were a programming language ,how many tests are required to achieve 100% statement coverage?
1. If x=3 then
2. Display_messageX;
3. If y=2 then
4. Display_messageY;
5. Else
6. Display_messageZ;
7. Else
8. Display_messageZ;
2. Display_messageX;
3. If y=2 then
4. Display_messageY;
5. Else
6. Display_messageZ;
7. Else
8. Display_messageZ;
A. 1
B. 2
C. 3
D. 4
18. 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
19. Using the same code example as question 17,how many tests are required to achieve 100% branch/decision coverage?
A. 1
B. 2
C. 3
D. 4
20. A test design technique is
A. A process for selecting test cases
B. A process for determining expected outputs
C. A way to measure the quality of software
D. A way to measure in a test plan what has to be done
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| A | C | D | C | A | D | C | C | D | D |
| 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| B | D | B | C | C | B | C | D | C | A |
No comments:
Post a Comment