The document describes four types of software testing for Category-5: unit testing, integration testing, functional testing, and requirement testing. Unit testing involves testing individual code modules during development to find and fix bugs early. Integration testing checks the interaction between modules by testing combined units. Functional testing verifies that software meets requirements by providing inputs and checking outputs. Requirement testing is performed by end users to check the intended use and accept the software prior to production.
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
0 ratings0% found this document useful (0 votes)
89 views
GAMP5 Testing Types
The document describes four types of software testing for Category-5: unit testing, integration testing, functional testing, and requirement testing. Unit testing involves testing individual code modules during development to find and fix bugs early. Integration testing checks the interaction between modules by testing combined units. Functional testing verifies that software meets requirements by providing inputs and checking outputs. Requirement testing is performed by end users to check the intended use and accept the software prior to production.
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
You are on page 1/ 1
CSV Testing Types for Category-5
Unit Testing Integration Testing Functional Testing Requirement Testing
Testing of Codes. Modules- Combinations As name indicates Checks users intended During Development of units. testing to verify use. phase. Testing of Interaction functional requirement User Acceptance Test. Unit-Smallest testable between modules. specifications. Testing performed by part. Checks flow of Data. Purpose is to test the end user or the Problems/bugs solved The purpose is to each function of the client to in early stage. expose defects in the software application, verify/accept the interaction between by providing software system before Scope of code chnge is software modules. appropriate input, moving the software there for Developers. verifying the output application to the Tools – HTMLUnit, Tools- Citrus, LDR against the Functional production PHPUnit, JUnit etc. etc. requirements. environment. Mainly involves black box testing and it is not concerned about UAT Requirement the source code of the User Requirement Specification Testing application. Checks User Interface, Functional Functional APIs, Database, Specification Testing Security, Client/Server Design Integration communication and Specification Testing other functionality of the Application. Developmen Production t Module/Unit Module/Unit Done either manually Specification Testing or using automation [Tools-Selenium] Code Modules