A. Writing a test summary report for stakeholders

B. Logging the outcome of test execution

C. Repeating test activities as a result of action taken for each discrepancy.

D. Evaluating testability of the requirements and system

A. d, a, c, b

B. a, d, b, c

C. a, b, c, d

D. a, b, d, c

A. b, c and d

B. a, d and f

C. a, d and e

D. b, c and f

A. 5, 6, 20

B. 4, 5, 80

C. 4, 5, 99

D. 1, 20, 100

A. b and c

B. a and c

C. b and d

D. c and d

A. They are more effective at finding faults than formal test design techniques

B. They are useful when there is limited experience in the test team

C. They can evaluate the reliability of a test object by attempting to force specific failures to occur

D. They are less structured than other experience-based techniques

A. 1, 2, 3, 5.

B. 1, 4, 6, 7.

C. 2, 3, 4, 7.

D. 3, 4, 5, 6.

A. An error

B. A fault

C. A failure

D. A defect

A. Time, Resources, and Risk

B. Verification, Validation, and Defect Reporting

C. Time, Organizational, and Cultural

D. None of the above

A. Because configuration management assures that we know the exact version of the testware and the test object

B. Because test execution is not allowed to proceed without the consent of the change control board

C. Because changes in the test object are always subject to configuration management

D. Because configuration management assures the right configuration of the test tools

A. Because the tools for automated testing require too much effort for learning

B. Because the maintenance of the test system is difficult

C. Because the test robot tools are restricted in their ability to recognize outputs

D. Because the test robot needs to be supported by a test management.

A. As there are many different ways to test software, thought must be given to decide what will be the most effective way to test the project on hand.

B. Starting testing without prior planning leads to chaotic and inefficient test project

C. A strategy is needed to inform the project management how the test team will schedule the test-cycles

D. Software failure may cause loss of money, time, business reputation, and in extreme cases injury and death. It is therefore critical to have a proper test strategy in place.

A. Statement Coverage = 1, Branch Coverage = 2

B. Statement Coverage = 2, Branch Coverage = 2

C. Statement Coverage = 1, Branch Coverage = 3

D. Statement Coverage = 2, Branch Coverage = 4

A. Ability to detect tiny changes that a human could not

B. Easy to implement and maintain

C. Test assets are more consistent

D. Ease of measurement of software quality

A. Test data preparation tools

B. Early defect detection

C. Scribe

D. Compilers

A. Controlled library access

B. Record of changes to documentation over time

C. Auditing conformance to ISO9001

D. Identification of test versions

A. iv - v - iii - ii - i

B. v - i - iii - ii - iv

C. iv - v - i - iii - ii

D. v - ii - iii - i - iv

A. The Condition Coverage ensures all paths through a module are executed whereas the Modified Condition Decision Coverage ensures each path in a decision can independently affect the outcome.

B. The Modified Condition Decision Coverage ensures all alternative paths are executed whereas the Condition Coverage ensure all main paths are executed.

C. The Condition Coverage ensures each condition takes all possible outcomes at lease once whereas the Modified Condition Decision Coverage requires both maximum and minimum values within each field.

D. The Modified Condition Decision Coverage relies on the tester's skill and past experience whereas the Condition Coverage relies on the way in which the system moves from one condition to another.