Attend a tool exhibition

Invite a vendor to give a demo

Analyse your needs and requirements

Find out what your budget would be for the tool

A small team to establish the best way to use the tool

Everyone who may eventually have some use for the tool

The independent testing team

The vendor contractor to write the initial scripts

The use of a variable before it has been defined

Unreachable (“dead”) code

Whether the value stored in a variable is correct

The re-definition of a variable before it has been used

Equivalence partitioning

State transition testing

LCSAJ

Syntax testing

Performed by customers at their own site

Performed by customers at their software developer’s site

Performed by an independent test team

Useful to test bespoke software

developers would typically use i, iv and vi; test team ii, iii and v

developers would typically use i and iv; test team ii, iii, v and vi

developers would typically use i, ii, iii and iv; test team v and vi

developers would typically use ii, iv and vi; test team I, ii and v

finding faults in the system

ensuring that the system is acceptable to all users

testing the system with other systems

testing for a business perspective

black box design techniques all have an associated measurement technique

white box design techniques all have an associated measurement technique

black box measurement techniques all have an associated test design technique

white box measurement techniques all have an associated test design technique

inspection is the most formal review process

inspections should be led by a trained leader

managers can perform inspections on management documents

inspection is appropriate even when there are no written documents

generating expected outputs

replaying inputs according to a programmed script

comparison of expected outcomes with actual outcomes

recording test inputs

re-testing is running a test again; regression testing looks for unexpected side

re-testing looks for unexpected side effects; regression testing is repeating

re-testing is done after faults are fixed; regression testing is done earlier

re-testing uses different environments, regression testing uses the same

only important in system testing

only used in component testing

most useful when specified in advance

derived from the code

report on deviations from the project plan

sign the system off for release

re-allocate resource to meet original plans

raise incidents on faults that they have found

a dynamic analysis tool

a debugging tool

a test management tool

a configuration management tool

how to fix the fault

how to reproduce the fault

test environment details

severity, priority

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

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

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

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

performance, load and stress testing

requirements-based testing

usability testing

top-down integration testing

expected outcomes are defined by the software’s behaviour

expected outcomes are derived from a specification, not from the code

expected outcomes include outputs to a screen and changes to files and

expected outcomes should be predicted before a test is run

ISO/IEC 12207

BS7925-1

BS7925-2

ANSI/IEEE 829

Is not important

Increases as we move the product towards live use

Decreases as we move the product towards live use

Is more expensive if found in requirements than functional design