What is not to be tested

Test environments

Quality plans

Schedules and deadlines

No, because they are normally applied before testing

No, because they do not apply to the test documentation

Yes, because both help detect faults and improve quality

Yes, because testing includes all non-constructive activities

Measuring response time

Measuring transaction rates

Recovery testing

Simulating many users

After more formal techniques have been applied

By inexperienced testers

After the system has gone live

Only by end users

Deviation from expected result to actual result

Defect in the software.

Error in the program code.

Fault in the system.

Analysts

Management

Developers

Testers

Regression testing.

Integration testing.

Error Guessing.

System testing.

Performance testing

Recovery testing

GUI testing

User requirements.

1

2

3

4

number of independent paths in the basis set of a program

number of binary decisions + 1

upper bound for the number of tests that must be conducted to ensure that all statements have been executed at least once

number of branches and decisions

23, 24, 25

0, 12, 25

30, 36, 39

32,37,40

1-b, 2-c, 3-a

1-b, 2-a, 3-c

1-c, 2-a, 3-b

1-a, 2-b, 3-c

Random testing

Data Flow testing.

Statement testing.

Syntax testing.

Ensure the test item is adequately tested.

Make the need for black-box testing redundant.

Run the risk that the requirements are not satisfied.

Suffices for the unit testing phase.

1-d, 2-c, 3-d, 4-a.

1-d, 2-a, 3-c, 4-b.

1-a, 2-b, 3-d, 4-c.

1-c, 2-b, 3-a, 4-d.

Review process itself

Metrics analysis

Tool support.

Process improvement.

System integration

Functional testing

Non-functional testing.

Requirements testing

Dynamic analysis tool

Static Analysis tool

Maintenance tool

Configuration tool

Dynamic analysis tool

Static Analysis tool

Maintenance tool

Configuration tool

Features to be tested.

Environmental needs.

Suspension criteria.

Expected results.