A. Since incidents are the discrepancies between actual and expected outcomes they cannot be raised during development

B. The discrepancies between actual and expected outcomes need to be logged as incidents

C. Incidents should be tracked from discovery and classification to correction and confirmation of the solution.

D. Incidents may be raised during development, review, testing or use of a software product

A. The test cases are designed to find defects in the data flow.

B. The test cases are designed to be used by real users, not by professional testers.

C. The test cases are designed to find defects in the process flow.

D. The test cases are always designed by customers or end users.

A. No The cost of testing cannot be measured effectively, so it is incorrect to use cost as an exit criteria

B. Yes Going by cost as an exit criteria constrains the testing project which will help achieve the desired quality level defined for the project

C. No The financial value of product quality cannot be estimated so it is incorrect to use cost as an exit criteria

D. Yes. Spending too much money on testing will result in an unprofitable product, and having cost as an exit criteria helps avoid this

A. Negligible effort to maintain the test assets generated by the tool

B. More subjective assessment

C. Availability of the test automation tool vendor

D. Reduction in repetitive manual work

A. Specification based techniques can be used as a substitute for a poorly defined test basis

B. Exploratory testing can replace black box techniques when testing time is very limited

C. Test execution scheduling should give priority to experienced based testing

D. Experienced based techniques are systematic and produce detailed test documentation

A. I, III. V

B. II. III. IV

C. II, III. V

D. II,1V

A. A white-box test technique which covers the decision results which determine the next statement to be executed

B. A black-box test technique which uses a state table to derive test cases

C. An experience-based lest technique in which test cases are based on the tester's knowledge of past failures

D. A white-box test technique which focuses on the percentage of executable statements that has been executed by a test suite

A. Acceptance criteria, completion criteria, pass/fail criteria.

B. Cost overruns.

C. Coverage of code, schedule, estimates of defect density.

D. The last executable statement within a component.

A. Suggested solution, priority and number of defects assigned to this developer.

B. Status of the incident, degree of impact, Test Case Number.

C. Line of code, number of defects found, time of day.

D. History, related defects and expected fix time.

A. (i) = S2 - S3 - S4 - S4 - S2 and (ii) = S2 -S3 - S4 -S4 - S4

B. (i) = S1 - S2 - S3 - S4 - S4 and (ii) = S2 -S4 - S4 - S4 - S2

C. (i) = S1 - S2 - S3 - S4 - S2 and (ii) = S4 - S2 - S4 - S4 - S4

D. (i) = S2 - S3 - S4 - S2 - S2 and (ii) = S4 - S2 - S4 - S4 - S4

A. I, ll

B. l, III IV

C. II, III, IV, V

D. I, II. Ill

A. Another term for testing system integrity

B. Looking for faults in larger components or subsystems

C. Specifying which components to integrate in which order

D. Testing that the interfaces work correctly

A. Number of test plan review comments

B. Percentage of tasks complete in test environment preparation

C. Percentage of planned test cases designed

D. Number of Test cases passed and failed

A. Boundary value analysis

B. Statement coverage

C. State transition testing

D. Equivalence partitioning