To find faults in the software.

To demonstrate that the software doesn’t work.

To assess whether the software is ready for release.

To prove that the software is correct.

Validation

Debugging

Testing

Verification

Damaged reputation

Inadequate training

Lack of methodology

Regulatory compliance

find as many faults as possible.

test high-risk areas.

obtain good test coverage.

test whatever is easiest to test.

time runs out.

no more faults are found.

the required level of confidence has been achieved.

the users won’t find any serious faults.

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.

time runs out.

the required level of confidence has been achieved.

no more faults are found.

the users won’t find any serious faults.

It does not require familiarity with the code.

It is cheaper than using developers to test their own code.

It avoids author bias in defining effective tests.

Testers are better at finding defects than developers.

Finding defects

Gaining confidence about the level of quality and providing information

Preventing defects.

Debugging defects

Fault - iv, Error - ii, Failure - i

Fault - iii, Error - ii, Failure - iv

Fault - ii, Error - iii, Failure - i

Fault - iii, Error - iv, Failure - i

Test Implementation and Execution

Test Analysis and Design

Test Planning and Control

Evaluating Entry Criteria and Reporting

Testing improves quality in itself

Testing ensures that the right version of code is

Testing can be used to assess quality

Testing shows that the software is error free

Test planning ensures the level of detail in test procedures is appropriate for test execution

Test planning schedules test execution but does not assign resources

Test planning defines the overall approach to testing but does not schedule specific activities such as test execution

Test planning identifies test objectives related to scope and risk but does not define the level of detail for test procedures used in test execution

Commercial off the shelf software

Compliance of the software

Change control of the software

Capable off the shelf software

finding faults in the system

ensuring that the system is acceptable to all users

testing the system with other systems

testing from a business perspective

I. Early test analysis and design.

II. Different test levels are defined with specific objectives.

III. Testers will start to get involved as soon as coding is done.

I and II.

Is only run once.

Will always be automated.

Will check unchanged areas of the software to see if they have been affected.

Will check changed areas of the software to see if they have been affected.

Performed by customers at their own site.

Performed by customers at the software developer's site.

Performed by an independent test team.

Useful to test software developed for a specific customer or user.

Testers should participate in reviewing documents as soon as they are approved

Test design should begin immediately after the corresponding development activity has ended

Each test level on a project shares the same test objectives

For every development activity, there is a corresponding test activity

Component Testing

System Testing

Integration Testing

Acceptance Testing

Component Testing

System Testing

Integration Testing

Acceptance Testing

Quality is fitness for use.

Quality is measured by looking at the attributes of the product.

Quality is based on good manufacturing processes, and meeting defined requirements

All of the above

It prevents developers from suing testers

International laws require software testing for exported products

Contracts may specify testing requirements that must be fulfilled

Testing across systems must be accompanied by legal documentation

Component Testing

System Testing

Integration Testing

Acceptance Testing