Tag: testing

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

System tests are often performed by independent teams.

Functional testing is used more than structural testing.

End-users should be involved in system tests

Faults found during system tests can be very expensive to fix.

Integration testing

Regression testing

System testing

User acceptance testing