SYSTEMS TESTING LIFE CYCLE – Test Levels

MANUAL

Testing Levels

ContentsUnit Testing System Testing

Integration Testing

Acceptance Testing

Unit Testing (Component Testing) Test each module / component / Program/

Database module individually. Follows a white box testing -- Developers will be involved Verifies the program specifications to the internal

logic of the program or module and validates the logic.

Tests are based upon: Component Requirements, Detailed Design , Code

May include functional as well as specific non-functional characteristics such as memory leaks as well as structural testing (eg: decision coverage)

Defects are typically fixed as soon as they are found, without formally managing these defects.

Unit Testing (Component Testing)

Testing Levels

ContentsUnit Testing System Testing

Integration Testing

Acceptance Testing

System Testing Confirms that the system as a whole delivers the

functionality originally required, using SRS

Follows the black box testing.

An Independent Test Team

Tests are based upon: SRS, Use cases, FS and Risk Analysis Reports

System Testing Functional Testing

Requirement BasedBusiness Process Based

Non – Functional System Testing Load , Performance and Stress Testing Usability Testing Configuration and Installation Testing Reliability Testing Back up and Recovery Testing Documentation Testing

Testing Levels

ContentsUnit Testing System Testing

Integration Testing

Acceptance Testing

Integration testing Tests interfaces between components, interactions with different parts of a

system and interfaces between systems.

Tests are based upon: System design, communications, use cases and architecture. Follow a Grey box testing

(Combination of WBT & BBT)

Both Testers and Developers will be involved

Component Integration and System Integration Testing

Integration Testing System Integration Testing(SIT) Verifies the integration of all applications.

Includes interfaces internal and external to the organization, with their hardware , software and infrastructure components.

Carried out in a production like environment.

Testing Levels

ContentsUnit Testing System Testing

Integration Testing

Acceptance Testing

Acceptance Testing The goal is to establish confidence in the system,

parts of the system or specific non – functional characteristics of the system.

It depends on the User requirements, System requirements, Use cases, Business processes.

Finding defects is not the main focus. Assess the system’s readiness for deployment and

use

Acceptance Testing Typical Test Objects

Operational and Maintenance processesBusiness ProcessesUser proceduresFormsReportsConfiguration Data

It is often the responsibility of the customers or users of a system (other stakeholders may be involved)

Acceptance Testing

Acceptance testing may occur at various times in the life cycle:

A COTS software product may be acceptance tested when it is installed or integrated.

Acceptance testing of the usability of a component may be done during component testing

Acceptance testing of a new functional enhancement may come before system testing.

Acceptance Testing Types of Acceptance Testing: User Acceptance Testing Operational (Acceptance) Testing Contract and regulation acceptance testing Alpha and Beta (or field) testing

Acceptance Testing User Acceptance Testing

Verifies the fitness for use of the system by end users Operational (Acceptance) Testing

Acceptance by the system administrators includes: testing backup/restore, disaster recovery, User management , maintenance tasks. Data Load and migration, periodic checks of security vulnerabilities

Acceptance Testing Contract and regulation acceptance testing

For producing custom-developed s/w. acceptance criteria should be defined when the parties agree to the contract. Regulation acceptance testing is performed against any regulations adhered to government or legal or safety

Alpha Testing Performed at developers site but not by developing team

Beta TestingTesting is done by customers at their locations