b. during the design stage
c. when the requirements have been formally documented
d. as soon as possible in the development life cycle
b. Poor software and poor testing
c. bad luck
d. insufficient time for testing
b. to decide when the software is of sufficient quality to release
c. to find as many bugs as possible before release
d. to give information for a risk based decision about release
b. The acceptance test does not necessarily include a regression test
c. Verification activities should not involve testers (reviews, inspections etc)
d. Test environments should be as similar to production environments as possible
b. firm about insisting that a bug is not a “feature” if it should be fixed
c. diplomatic, sensitive to the way they may react to criticism
d. All of the above
b. the most difficult tests first(to allow maximum time for fixing)
c. the easiest tests first(to give initial confidence)
d. the order they are thought of
b. wages are rising
c. the fault has been built into more documentation,code,tests, etc
d. none of the above
b. should be able to understand the source code.
c. is highly motivated to find faults
d. is creative to find the system’s weaknesses
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
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
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.
b. no change
c. increasing test time
d. can’t say
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
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
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.
b. the objective of the test
c. how appropriate the technique is for testing the application
d. whether there is a tool to support the technique
2. Display_messageX;
3. If y=2 then
4. Display_messageY;
5. Else
6. Display_messageZ;
7.Else
8. Display_messageZ;
b. 2
c. 3
d. 4
b. 2
c. 3
d. 4
b. Usability
c. Performance
d. Security
b. Coverage analysis
c. Dynamic analysis
d. Memory analysis
b. IEEE610
c. BS7925-1
d. BS7925-2
b. IEEE 610
c. BS7925-1
d. BS7925-2
b. Faults in code are the most expensive to fix.
c. Faults in requirements are the most expensive to fix
d. Faults in designs are the most expensive to fix.
b. Big-bang
c. Bottom-up
d. Top-down
b. equivalence partitioning
c. error- guessing
d. usability testing
b. Small
c. Difficult to write
d. Difficult to test
b. coverage analysis
c. usability assessment
d. installation test
b. glass box
c. structural
d. functional
b. 3,20,21
c. 3,10,22
d. 10,21,22
b. 9,10,21,22
c. 10,11,21,22
d. 10,11,20,21
1. d
2. b
3. d
4. c
5. d
6. a
7. c
8. b
9. a
10. a
11. c
12. a
13. b
14. c
15. b
16. b
17. c
18. c
19. a
20. c
21. b
22. d
23. c
24. a
25. b
26. d
27. a
28. d
29. c
30. b










