reduces the time spent by the testers

reduces the resources spent (hardware)

mostly used in web testing

all of the above

identifying defects.

fixing defects.

1 and 2

None

Shows the number of newly discovered defects per unit time

Shows the number of open defects per unit time.

Shows the cumulative total number of defects found up to this time.

Any of these, depending on the company.

The probability the negative event will occur

The potential loss or impact associated with the event

Both a and b

Neither a nor b

The failure occurs only if you reach a statement taking the TRUE branch of an IF statement, and you got to the statement with a test that passed through the FALSE branch.

The failure depends on the program's inability to handle specific data values, rather than on the program's flow of control.

Both A and B

We are not required to test code that customers are unlikely to execute.

Test manager

Test engineer

both A & B

Project Manager

Use risk based analysis to find out which areas need to be tested

Use automation tool for testing

a and b

None of the above

A. ii, iv and v.

B. ii, iii and iv.i,

C. i, ii and iv.

D. i, iii and v.

A. Scheduling test analysis and design tasks.

B. Initiating corrective actions.

C. Monitoring progress and test coverage.

D. Measuring and analyzing results.

A. At system and acceptance testing levels only.

B. At all test levels.

C. At all levels above integration testing.

D. At the acceptance testing level only.

A. To identify potential application failures by use of a test specification.

B. To identify defects in any software work product.

C. To identify spelling mistakes in a requirements specification.

D. To identify standards inconsistencies in the code.

A. Developers.

B. Analysts.

C. Testers.

D. Incident Managers.

ii, iv and v.

ii, iii and iv.i,

i, ii and iv.

i, iii and v.

Scheduling test analysis and design tasks.

Initiating corrective actions.

Monitoring progress and test coverage.

Measuring and analyzing results.

At system and acceptance testing levels only.

At all test levels.

At all levels above integration testing.

At the acceptance testing level only.

To identify potential application failures by use of a test specification.

To identify defects in any software work product.

To identify spelling mistakes in a requirements specification.

To identify standards inconsistencies in the code.

Developers.

Analysts.

Testers.

Incident Managers.

Shared

Local

Both

None

Multiple

Two

Three

Seven

Object Repositories dialog box

Object Repositories Manager dialog box

Associate Repositories Manager dialog box

Associate Repositories dailog box