A. I, II, III, IV and V.

B. IV, I, V, III and II.

C. IV, I, V, II and III.

D. I, IV, V, III and II.

A. Show that the system works before we ship it.

B. Find as many defects as possible.

C. Reduce the overall level of product risk.

D. Prevent defects through early involvement.

A. Test management and control

B. Test specification and design

C. Test execution and logging

D. Performance and monitoring

A. W, X and Y

B. V, Y and Z

C. V, W and Z

D. X, Y and Z

A. An input, expected outcome, pre-condition and post-condition

B. The steps to be taken to get the system to a given point

C. Something that can be tested

D. A specific state of the software, e.g. before a test can be run

A. I is true; II, III and IV are false

B. II is true; I, III and IV are false

C. I and II are true; III and N are false

D. II and III are true; I and IV are false

A. 15, 19 and 25 degrees

B. 17, 18, 20 and 21 degrees

C. 18, 20 and 22 degrees

D. 16 and 26 degrees

A. Security testing

B. Non-functional testing

C. Exploratory testing

D. Interoperability testing

A. To confirm the users' confidence that the system will meet their business needs.

B. To confirm that a defect has been fixed correctly.

C. To confirm that no unexpected changes have been introduced or uncovered as a result of changes made.

D. To confirm that the detailed logic of a component conforms to its specification.

A. Acquiring the best tool and ensuring that all testers use it.

B. Adapting processes to fit with the use of the tool and monitoring tool use and benefits.

C. Setting ambitious objectives for tool benefits and aggressive deadlines for achieving them.

D. Adopting practices from other successful organizations and ensuring that initial ways of using the tool are maintained.

A. Testing performed to expose faults in the interfaces and in the interaction between integrated components.

B. Testing to verify that a component is ready for integration.

C. Testing to verify that the test environment can be integrated with the product.

D. Integration of automated software test suites with the product.

A. Is part of the fundamental testing process.

B. Includes the repair of the cause of a failure.

C. Involves intentionally adding known defects.

D. Follows the steps of a test procedure.

A. Insufficient funds were available to pay the interest rate calculated.

B. Insufficient calculations of compound interest were included.

C. Insufficient training was given to the developers concerning compound interest alculation rules.

D. Inaccurate calculators were used to calculate the expected results.

A. 0, 9,19, 49, 50, 74, 75, 99,100

B. 10, 50, 75,100, 250, 1000

C. 0, 1,10,11, 50, 51, 75, 76,100,101

D. 25, 26, 35, 36, 45, 46, 55, 56

A. The process of anticipating or guessing where defects might occur.

B. A systematic approach to identifying specific equivalent classes of input.

C. The testing carried out by a chartered engineer.

D. Concurrent test design, test execution, test logging and learning.

A. 9 out of 10 decision outcomes have been exercised by this set of tests.

B. 9 out of 10 statements have been exercised by this set of tests.

C. 9 out of 10 tests have been run on this set of software.

D. 9 out of 10 requirements statements about the software are correct.

A. Master test plan

B. System test plan

C. Acceptance test plan

D. Project plan

A. The analysis of batch programs

B. The reviewing of test plans

C. The analysis of program code or other software artifacts

D. The use of black-box testing

A. Impossibility of exhaustive testing.

B. Importance of early testing.

C. The absence of errors fallacy.

D. Defect clustering.

A. Only I is a configuration management task.

B. All are configuration management tasks.

C. I, II and III are configuration management tasks.

D. I, II and IV are configuration management tasks.

A. II, III and IV are possible explanations, but I and V are not possible.

B. All five are possible explanations.

C. I, IV and V are possible explanations, but II and III are not possible.

D. III, IV and V are possible explanations, but I and II are not possible.

A. A separate scribe during the logging meeting

B. Trained participants and review leaders

C. The availability of tools to support the review process

D. A reviewed test plan

A. I and III

B. I and IV

C. II and III

D. II and IV

A. I and III

B. II and III

C. II and IV

D. III and IV

A. Decision tables and state transition testing

B. Equivalence partitioning and state transition testing

C. Decision tables and boundary value analysis

D. Equivalence partitioning and boundary value analysis

A. Independent testers don't have to spend time communicating with the project team.

B. Programmers can stop worrying about the quality of their work and focus on producing more code.

C. The others on a project can pressure the independent testers to accelerate testing at the end of the schedule.

D. Independent testers sometimes question the assumptions behind requirements, designs and implementations.

A. DDP = {Defects (Testers) + Defects (Field)} / Defects (Testers)

B. DDP = {Defects (Testers) + Defects (Field)} / Defects (Testers)

C. DDP = Defects (Testers) / {Defects (Field) + Defects (Testers)}

D. DDP = Defects (Testers) / {Defects (Field) - Defects (Testers)}

A. Inspection results and modification.

B. Migration and inspection results.

C. Migration and retirement of the system.

D. Alpha testing results and migration.

A. Equivalence partitioning

B. Boundary value analysis

C. Decision tables

D. All three described above

A. It is probable that subsystem C has still more hidden defects. Therefore we need to test subsystem C in more detail.

B. Because we have already found many defects in subsystem C, we should concentrate testing resources n Subsystem A.

C. Observed defect density does not allow any conclusions about the amount of additional testing.

D. We should try to equalize the amount of testing over all modules to ensure that we test all subsystems evenly.

A. Static analysis tools can change the code to reduce complexity.

B. Static analysis tools are intended to support developers only.

C. Static analysis tools aid in understanding of code structure and dependencies.

D. Static analysis tools cannot be used to enforce coding standards.

A. Reliability measures, number of tests written, and product completeness.

B. Thoroughness measures, reliability measures, cost, schedule, tester availability and residual risks.

C. Thoroughness measures, reliability measures, test cost, amount of time spent testing and product completeness, number of defects.

D. Time to market, residual defects, tester qualification, degree of tester independence, thoroughness measures and test cost.

A. Testing ensures that the system under test will not error out in a production environment.

B. Testing identifies defects which ensures a successful product will be released to market.

C. Testing increases the quality of a software system by avoiding defects in the system under test.

D. Testing through verification and validation of functionality identifies defects in the system under test.

A. Two equivalence partitions.

B. Three equivalence partitions.

C. Four equivalence partitions.

D. Five equivalence partitions.

A. I

B. IV

C. I and IV

D. I and III

A. Integration of automated software test suites with the application under test.

B. Testing performed to expose faults in the interaction between components and systems.

C. Testing to verify that a component is ready for integration with the rest of the system.

D. Testing to verify that the test environment can be integrated with the product.

A. The product crashed when the user selected an option in a dialog box.

B. One source code file included in the build was the wrong version

C. The computation algorithm used the wrong input variables.

D. The developer misinterpreted the computational requirement for that algorithm.

A. Testing shows failures that are caused by defects. Debugging finds, analyzes, and removes the causes of failures in the software.

B. Testing pinpoints the defects. De bugging analyzes the faults and proposes preventing activities.

C. Testing removes faults. Debugging identifies the causes of failures.

D. Dynamic testing prevents causes of failures. Debugging removes the failures.

A. To help the developer to compare differences between files and databases.

B. To reduce the quantity of component tests needed to be run.

C. To make it easier for developers to peer-test each other's code.

D. To simplify running unit tests when related components are not available yet.