Unit / Module Testing

Unit testing is a verification effort on the smallest unit of the software design – the software component or module. Unit testing is
white-box oriented, and this can be conducted in parallel for multiple components.

Unit testing is mainly focused on following areas

Entry Criteria
Availability of modules.
Stable build

Activities
Preparation of Unit Test Plan.
Preparation of Unit Test cases.
‘Preparation’/ ‘CLIENT shall Provide’ Test data for Unit test cases
Execution of test cases.

Deliverables
Unit test plan Document
Unit Test Case Document
Test Data for Unit Test Cases
Test Status Report

Proof of Execution
Review of Unit Test Plan
Traceability Matrix for all Unit Test Cases
Review of Test Document
Success messages for passed test cases and screen shots for failed test cases

Exit Criteria
Sign off Unit Test plan Document.
Sign of Unit Test Case Document
Frozen Test Document
2 rounds of Test Execution

Integration Testing

The primary objective of integration testing is to discover errors in the interfaces between Modules / Sub- Systems.

Techniques/Approaches for Integration testing:

Top-Down approach: is an incremental approach to testing of the program structure.
Modules are integrated by moving downward through the control hierarchy, beginning
with the main control module, this could be done as depth- first or breadth-first manner.

Bottom-up approach: as the name implies, begins construction and testing with atomic
modules i.e., from the components at the lowest levels in the program structure

Entry Criteria
Unit testing of all Modules is Signed off

Activities
Preparation of Integration Test Plan.
Preparation of Integration Test Scenarios.
Execution of test Scenarios.

Deliverables
Integration Test Plan Document
Integration Test scenarios Document.
Test Status report.

Proof of Execution
Review of Integration Test Plan
Traceability Matrix for the all Integration test Scenarios
Success messages for passed test scenarios and screen shots for failed test scenarios

Exit Criteria
Sign off Integration Test plan Document.
Sign off Integration test Scenarios Document.
Sign off Integration testing. 

System Testing

The primary objective of system testing is to discover errors when the system is tested as
a whole. System testing is also called as End-To-End Testing.

System testing is mainly focused on following areas

Identifying the End-To-End / Business Life Cycles.
Design the test and data.
Optimize the End-End / Business Life Cycles.

Entry Criteria
Successful completion of integration testing.
Execution of test cases.

Activities
Preparation of System Test Plan.
Preparation of System Test cases.
‘Preparation’/ ‘CLIENT shall provide test data for System test cases

Deliverables
System Test Plan Document
System Test Case Document.
Test data document for System Test cases
Test Status report.

Proof of Execution
Review of system test plan document
Traceability matrix for the all System test cases.
Review of test data document for system testing
Success messages for passed test cases and screen shots for failed test cases

Exit Criteria
Sign off system test plan document.
Sign off System test scenarios document.
Frozen test data Document
Sign off system testing.

Top