Testing Methodologies
Testing Methodologies / Testing Strategies:
Testing Methodology is a Scheme / Approach / Strategy that explains what kind of methodology can be utilized at different phases of the SDLC.
Testing Methodologies are also called testing strategies.
There are 3 Testing Methodologies available.
1) Black Box Testing
2) White Box Testing
3) Gray Box Testing
1) Black Box Testing:
(This is especially for Testers).
It is also called as Functional Testing (Functional based Testing).
It is also called as requirements based Testing.
Definition: The process of testing the application without consideration of the code but with consideration of the Functionalities / Requirements of the application.
In Black Box Testing, Testers will never bother about the code and Testers will not bother about the software environments. (Software environment = coding language).
Testers will mainly focus on requirements and the behavior of the application (Functionality of the application), based on the functional requirements testers will have to design test plans and test cases.
And later what is the coding is done application build is release to QA and now testers will execute the Functional Test Cases on the application build.
Black Box testing has the following testing types as part of it.
1) Smoke Testing
2) Functional Testing.
3) Integration Testing
4) System Testing
5) Regression Testing
6) Automation Testing
7) UAT
2) White Box Testing:
(This is especially for developers).
This is also called structural testing (structural base to testing).
This is also called code based testing.
This is also called clear based testing.
Definition: The process of testing the application with consideration of the code (like loops, structures, conditional statements, Functions, Procedures, and Structures and so on) focusing the code level executions.
Developers consider each and every Module level code, all the loops, conditions, functions in their code and so foe such White Box Testing.
White Box testing as following testing types as part of it.
1) Unit Testing
a. Code base Testing
b. Statement coverage
c. Loops coverage
d. Functional coverage
e. Module coverage
2) Integration Testing
a. Top-down approach
b. Bottom-up approach
c. Hybrid-approach
3) Gray Box Testing:
The process of testing the application in both the considerations like considering the code and considering the functionalities of the application is called as Gray Box Testing.
This is also called as Hybrid Testing.
With the gray box testing methodology we lose both the White Box Testing methodology and Black Box testing methodology while testing the application.
Usually this kind of testing is carried out by the developers who have testing experience also (person = Dev + QA).
Posts
