$ 1500

$ 32001

$ 28000

$ 33501

$5800; $28000; $32000

$0; $200; $4200

$5200; $5500; $28000

$28001; $32000; $35000

Use of automated test execution tools.

Testing performed by users.

Testing against acceptance test criteria.

Integration of system with user documentation.

Be easy to maintain.

Be unlikely to cause a failure.

Never fail under any circumstances.

Be written according to coding standards.

Each test stage has a different purpose.

It is easier to manage testing in stages.

We can run different tests in different environments.

The more stages we have, the better the testing.

Regression testing

Integration testing

System testing

User acceptance testing

A minimal test set that achieves 100% LCSAJ coverage will also achieve 100% branch coverage.

A minimal test set that achieves 100% path coverage will also achieve 100% statement coverage.

A minimal test set that achieves 100% path coverage will generally detect more faults than one that achieves 100% statement coverage.

A minimal test set that achieves 100% statement coverage will generally detect more faults than one that achieves 100% branch coverage.

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.

3

4

5

6

Test coverage criteria can be measured in terms of items exercised by a test suite.

A measure of test coverage criteria is the percentage of user requirements covered.

A measure of test coverage criteria is the percentage of faults found.

Test coverage criteria are often used when specifying test completion criteria.

find as many faults as possible.

test high risk areas.

obtain good test coverage.

test whatever is easiest to test.

v-3,w-2,x-1,y-5,z-4

v-2,w-5,x-1,y-4,z-3

v-3,w-4,x-1,y-5,z-2

v-2,w-1,x-4,y-3,z-5

System tests are often performed by independent teams.

Functional testing is used more than structural testing.

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

End-users should be involved in system tests.

Incidents should always be fixed.

An incident occurs when expected and actual results differ.

Incidents can be analysed to assist in test process improvement.

An incident can be raised against documentation.

time runs out.

the required level of confidence has been achieved.

no more faults are found.

the users won’t find any serious faults.

Incident resolution is the responsibility of the author of the software under test.

Incidents may be raised against user requirements.

Incidents require investigation and/or correction.

Incidents are raised when expected and actual results differ.

syntax testing

equivalence partitioning

stress testing

modified condition/decision coverage

In a system two different failures may have different severities.

A system is necessarily more reliable after debugging for the removal of a fault.

A fault need not affect the reliability of a system.

Undetected errors may lead to faults and eventually to incorrect behaviour.

They are used to support multi-user testing.

They are used to capture and animate user requirements.

They are the most frequently purchased types of CAST tool.

They capture aspects of user behaviour.

Metrics from previous similar projects

Discussions with the development team

Time allocated for regression testing

a & b