Selenium Appium JMeter JUnit Postman Jira TestNG SoapUI
UIPath
Verification Validation
We check whether we are developing the We check whether the developed product
right product or not. is right.
Verification is also known as static Validation is also known as dynamic
testing. testing.
Verification includes different methods Validation includes testing like functional
like Inspections, Reviews, and testing, system testing, integration, and
Walkthroughs. User acceptance testing.
It is a process of checking the It is a process of checking the software
work-products (not the final product) of a during or at the end of the development
development cycle to decide whether the cycle to decide whether the software
product meets the specified follows the specified business
requirements. requirements.
Quality assurance comes under Quality control comes under validation
verification testing. testing.
The execution of code does not happen In validation testing, the execution of
in the verification testing. code happens.
In verification testing, we can find the In the validation testing, we can find
bugs early in the development phase of those bugs, which are not caught in the
the product. verification process.
Verification testing is executed by the Validation testing is executed by the
Quality assurance team to make sure testing team to test the application.
that the product is developed according
to customers' requirements.
Verification is done before the validation After verification testing, validation
testing. testing takes place.
In this type of testing, we can verify that In this type of testing, we can validate
the inputs follow the outputs or not. that the user accepts the product or not.
Selenium Appium JMeter JUnit Postman Jira TestNG SoapUI
UIPath
Static testing Dynamic testing
In static testing, we will check the code or In dynamic testing, we will check the
the application without executing the code/application by executing the code.
code.
Static testing includes activities like code Dynamic testing includes activities like
Review, Walkthrough, etc. functional and non-functional testing
such as UT (usability testing), IT
(integration testing), ST (System testing)
& UAT (user acceptance testing).
Static testing is a Verification Process. Dynamic testing is a Validation Process.
Static testing is used to prevent defects. Dynamic testing is used to find and fix
the defects.
Static testing is a more cost-effective Dynamic testing is a less cost-effective
process. process.
This type of testing can be performed
before the compilation of code.
Under static testing, we can perform the Equivalence Partitioning and Boundary
statement coverage testing and structural Value Analysis technique are performed
testing. under dynamic testing.
It involves the checklist and process This type of testing required the test
which has been followed by the test case for the execution of the code.
engineer.
▲
S. Black Box Testing White Box Testing
No.
1. It is a way of software testing in It is a way of testing the software in
which the internal structure or the which the tester has knowledge about
program or the code is hidden and the internal structure or the code or
nothing is known about it. the program of the software.
2. Implementation of code is not Code implementation is necessary for
needed for black box testing. white box testing.
3. It is mostly done by software It is mostly done by software
testers. developers.
4. No knowledge of implementation is Knowledge of implementation is
needed. required.
5. It can be referred to as outer or It is the inner or the internal software
external software testing. testing.
6. It is a functional test of the software. It is a structural test of the software.
7. This testing can be initiated based This type of testing of software is
on the requirement specifications started after a detailed design
document. document.
8. No knowledge of programming is It is mandatory to have knowledge of
required. programming.
9. It is the behavior testing of the It is the logic testing of the software.
software.
10. It is applicable to the higher levels It is generally applicable to the lower
of testing of software. levels of software testing.
11. It is also called closed testing. It is also called clear box testing.
12. It is the least time consuming. It is most time consuming.
13. It is not suitable or preferred for It is suitable for algorithm testing.
algorithm testing.
14. Can be done by trial and error ways Data domains along with inner or
and methods. internal boundaries can be better
tested.
15. Example: Search something on Example: By input to check and
google by using keywords verify loops
16. Black-box test design White-box test design techniques-
techniques- Control flow testing
Decision table testing Data flow testing
All-pairs testing Branch testing
Equivalence partitioning
Error guessing
17. Types of Black Box Testing: Types of White Box Testing:
Functional Testing Path Testing
Non-functional testing Loop Testing
Regression Testing Condition testing
18. It is less exhaustive as compared to It is comparatively more exhaustive
white box testing. than black box testing.
