Static Test Techniques

Software code

Requirements specification

Test designs

All of the above

Gives quality information about the code without executing it.

Checks expected results against actual results.

Can detect memory leaks.

Gives information about what code has and has not been exercised.

Walkthrough

Inspection

Informal review

Management approval

Inspections are led by a trained moderator, whereas technical reviews are not necessarily.

Technical reviews are led by a trained leader, inspections are not.

In a walkthrough, the author does not attend.

Participants for a walkthrough always need to be thoroughly trained.

An inspection is led by the authors, whilst a walk through is led by a trained moderator.

An inspection has a trained leader, whilst a walk through has no leader.

Authors are not present during inspections, whilst they are during walkthroughs.

A walkthrough is led by the author, whilst an inspection is led by a trained moderator.

s = 4, t = 3, u = 2 and 5, v = 1

s = 4 and 5, t = 3, u = 2, v = 1

Cs = 1 and 5, t = 3, u = 2, v = 4

s = 5, t = 4, u = 3, v = 1 and 2

With static analysis, defects can be found that are difficult to find with dynamic testing.

Compiling is not a form of static analysis.

When properly performed, static analysis makes functional testing redundant.

Static analysis finds all faults.

1 and 3 are true. 2 and 4 are false.

2 is true. 1, 3 and 4 are false.

2 and 3 are true. 1 and 4 are false.

2, 3 and 4 are true. 1 is false.

Unreachable code

Undeclared variables

Faults in the requirements

Too few comments