SOFTWARE

TESTING

PRESENTED BY:
VISHAL KUMAR (19CS-02)
VINEET KUMAR (19CS-24)
AAKASH ALI (19CS-49)
 CONTENTS:

 WHAT IS SOFTWARE TESTING?

 WHY SOFTWARE TESTING IS IMPORTANT?

 TYPES OF SOFTWARE TESTING?

 WHAT IS SOFTWARE TESTING?

 Testing: It is the process of executing a program with the

intention of finding errors.
OR
 Testing is a group of techniques to determine correctness
of the application.

 Software Testing: It is a method to check whether the

actual software product matches expected requirements
and ensure that software product is error free.
 In other words software testing is the process of verification
and validation.
 VERIFICATION & VALIDATION:

VERIFICATION VALIDATION

 Verification is the  Validation is process

process of confirming if of examining whether
the software by using the software meets
proper specifications the costumer
and methodologies. requirements.
 It does not involves the  It involves the
execution of code. execution of code.
 IMPORTANCE OF SOFTWARE TESTING:

 Software Testing is Important because if there are any

bugs or errors in the software, it can be identified early and
can be solved before delivery of the software product.
Properly tested software product ensures reliability, security
and high performance which further results in time saving,
cost effectiveness and customer satisfaction.
 TYPES OF SOFTWARE TESTING:
 software testing is a process of analyzing an application's functionality
as per the customer requirements.
 If we want to ensure that our software is bug-free or stable, we must
perform the various types of software testing because testing is the only
method that makes our application bug-free.
 MANUAL:
 It is performed by person or a software testing team.
 It does not uses any tool.
 It should be performed when experienced and talented testing experts
are available.
 It is less reliable and takes more time.

 AUTOMATION:
 It is performed by using software testing tools that executes a test script
that was written in advance .
 Any test that can be repeated occasionally during the development
process should be automated.
 It is faster and reliable as it runs using tools and pre-written test script.
 TYPES OF MANUAL TESTING:

1) WHITE BOX TESTING:

 In white-box testing, the developer will inspect every line of code before
handing it over to the testing team or the concerned test engineers.
 White box testing is also known as open box testing, glass box testing,
clear box testing, and transparent box testing.
 It tests internal coding and infrastructure of a software focus on checking
of predefined inputs against expected and desired outputs and
strengthening the security of the software.
 The developer performs the white box testing and sends the software to
the testing team where they will perform black box testing.
2) BLACK BOX TESTING:
 In this testing, the test engineer will analyze the software against
requirements, identify the defects or bug, and sends it back to the
development team.
 Then, the developers will fix those defects, do one round of White box
testing, and send it to the testing team.
 The main objective of implementing the black box testing is to specify
the business needs or the customer's requirements.

Black Box testing is further categorized into two pars:

i) Functional Testing.
ii) Non-Functional Testing.
i) Functional Testing.
 Functional testing is testing the ‘Functionality’ of a software or an
application under test.
 Functional testing ensures that the requirements are properly satisfied
by the application.
 Functional testing can be done manually.
 Functional testing is based on customer’s requirements.

ii) Non-Functional Testing.

 Non-functional testing is a type of software testing that is performed to
verify the non-functional requirements of the application.
 It tests all the aspects which are not tested in functional testing.
 Non Functional testing is based on customer’s expectations.
3) GREY BOX TESTING:

 Gray box testing is a combination of white-box testing and black-box testing.

Testers have partial knowledge of the internal structure or code of an
application.

 Grey Box testing commonly identifies context-specific errors that belong to web
systems. For example; while testing, if tester encounters any defect then he
makes changes in code to resolve the defect and then test it again in real time.
 It provides combined benefits of both Black box testing and White Box testing.
 It includes the input values of both developers and testers at the same time to
improve the overall quality of the product.
THANK YOU!!!