An inspection is lead by the author, whilst a walkthrough is lead by a trained moderator

An inspection has a trained leader, whilst a walkthrough has no leader.

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

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

It allows the identification of changes in user requirements

It facilitates timely set up of the test environment.

It reduces defect multiplication

It allows testers to become involved early in the project.

tests the individual components that have been developed.

tests interactions between modules or subsystems

only uses components that form part of the live system.

tests interfaces to other systems.

updating tests when the software has changed

testing a released system that has been changed

testing by users to ensure that the system meets a business need

testing to maintain business advantage

) It is easier to manage testing in stages

We can run different tests in different environments

Each test stage has a different purpose.

The more stages we have, the better the testing.

can only be used in component, integration and system testing.

supplements formal test design techniques.

is only performed in user acceptance testing.

is not repeatable and should not be used.

time runs out.

no more faults are found.

the users won’t find any serious faults.

the required level of confidence has been achieved.

Usability testing

Performance testing

Boundary value analysis

Security testing

the analysis of batch programs.

the analysis of program code

the reviewing of test plans.

the use of black box testing

performed by an Independent Test Team

performed by customers at the software developer’s site

performed by customers at their own site

performed as early as possible in the lifecycle

Poor quality software

bad luck

Poor software and poor testing

insufficient time for testing

Coverage analysis

Dynamic analysis

State analysis

Memory analysis

found in the software; the result of an error

an incorrect step, process or data definition in a computer program

departure from specified behavior

a human action that produces an incorrect result

An inspection is lead by the author, whilst a walkthrough is lead by a trained moderator.

An inspection has a trained leader, whilst a walkthrough has no leader

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

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

state transition testing

LCSAJ

boundary value analysis

syntax testing

) It facilitates timely set up of the test environment

It allows the identification of changes in user requirements.

It reduces defect multiplication

It allows testers to become involved early in the project

Actual results

Program specification

User requirements

System specification

possible communications bottlenecks in a program.

the rate of change of data values as a program executes

the use of data on paths through the code.

the intrinsic complexity of the code

The system shall be user friendly.

The safety-critical parts of the system shall contain 0 faults.

The response time shall be less than one second for the specified design load.

The system shall be built to be portable.

find as many faults as possible.

test high risk areas.

obtain good test coverage.

test whatever is easiest to test