Scribd
Upload
385 views3 pages

Levels of Software Testing Explained

The document describes 5 levels of software testing: unit testing, module testing, integration testing, system testing, and user acceptance testing. It provides details on the objectives and activities included in each level. Unit testing is done by developers to test individual program units. Module and integration testing are done by test engineers and involve testing groups of integrated units and modules. System testing tests the full application and user acceptance testing is done by customers in the live environment.

Uploaded by

Vineela Deekonda
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
385 views3 pages

Levels of Software Testing Explained

The document describes 5 levels of software testing: unit testing, module testing, integration testing, system testing, and user acceptance testing. It provides details on the objectives and activities included in each level. Unit testing is done by developers to test individual program units. Module and integration testing are done by test engineers and involve testing groups of integrated units and modules. System testing tests the full application and user acceptance testing is done by customers in the live environment.

Uploaded by

Vineela Deekonda
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

www.qatestingtraining.

com Levels of Testing:- 1) Unit Testing 2) Module Testing 3) Integration Testing 4) System Testing 5) User Acceptance Testing Unit testing: It is defined as an initial level of testing in which once the unit is developed it will be tested for its correctness, if it is justified the requirements. Unit testing belongs to white box testing as at this level no screen is available and program only be tested. Hence it is always done by developers. Module testing: Soon after units are developed to form single module if at all any are performs testing on it to check its operational perfection this type of testing is known module testing. The module testing belongs to black box testing as GUI is available at this level to check the functionality on it. Hence module testing is always done by test engineers. Integration testing: Once the modules are individually developed and tested for their perfection they are brought together to form an application. Once the modules are integrated if testing is performed on integrated modules it is known as integration testing. Purpose: 1. to check if the individual modules retain their perfection even after integration 2. to check the integrated behavior of these modules 3. To check if the data communication among the modules is as per DFDs of the technical design document. .

www.qatestingtraining.com System Testing Once the application is developed it has to be deployed into the customers specified simulated environment so as to prepare a system. (when once software is integrated to hardware it is said to be a system). If one performs testing on the system to check the operational behavior, performance, look and feel it is known as system testing. In a way system testing is a full fledged testing as it includes GUI testing, functional testing, load testing, performance testing, stress testing, security testing etc. Note: High level integration testing is covered under system testing. System testing belongs to Black Box testing and is always done by Test Engineers.

www.qatestingtraining.com User Acceptance Testing It is final level of testing in which the application is tested in the customer specified simulated live environment (Production Site) in the presence of the customer with in the development company(some times in the client place) to ensure the justification of acceptance criteria and it is designed to determine whether software is fit for use or not. The UAT belongs to Black Box testing and is done by test engineers/customers/end users. Note : This document may contain the similar notes or content which is available over internet for topic Levels of Testing

You might also like