Scribd
Upload
4 views

Types of TESTINGS

Uploaded by

mrrichie34
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
4 views

Types of TESTINGS

Uploaded by

mrrichie34
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

Types Of Testings:

*********************

1.SANITY TESTING :
---------------------
After the software build is created before releasing the build the test is
conducted to verify all the requirements are including in the build or not,
the build is working correct or not. If sanity test passed then only build is
released to testing team.

2. SMOKE TESTING :
----------------------
Whenever we received the software build, this is the first test to conducted to
verify all the basic functionalities as per the requirements,
this test conducted to verify we can accept the software build or not.
If any defect is found, we will stop testing and reject the build, Else we can
continue testing.
After Smoke test either the status pass or fail reported to the developer.

3. UNIT TESTING :
-------------------
Unit Testing is a type of software testing where individual units or components of
a software are tested.
The purpose is to validate that each unit of the software code performs as
expected.
Unit Tests isolate a section of code and verify its correctness. A unit may be an
individual function, method, procedure, module, or object.

4. INTEGRATION TESTING :
-----------------------------
Integration Testing is defined as a type of testing where software modules are
integrated logically and tested as a group.
A typical software project consists of multiple software modules, coded by
different programmers.
The purpose of this level of testing is to expose defects in the interaction
between these software modules when they are integrated.

Integration Testing focuses on checking data communication amongst these modules.


Hence it is also termed as ‘I & T’ (Integration and Testing),
‘String Testing’ and sometimes ‘Thread Testing’.

5 .SYSTEM TESTING :
-----------------------
System Testing is a level of testing that validates the complete and fully
integrated software product. The purpose of a system test is to evaluate
the end-to-end system specifications. Usually, the software is only one element of
a larger computer-based system. Ultimately, the software is interfaced
with other software/hardware systems. System Testing is defined as a series of
different tests whose sole purpose is to exercise the full computer-based system.

6. REGRESION TESTING :
---------------------------
Regression Testing is defined as a type of software testing to confirm that a
recent program or code change has not adversely affected existing features.
Regression Testing is nothing but a full or partial selection of already executed
test cases that are re-executed to ensure existing functionalities work fine.
This testing is done to ensure that new code changes do not have side effects on
the existing functionalities. It ensures that the old code still works once
the latest code changes are done.
7. WHITE BOX TESTING :
---------------------------
White Box Testing is a testing technique in which software’s internal structure,
design, and coding are tested to verify input-output flow and improve design,
usability, and security. In white box testing, code is visible to testers, so it is
also called Clear box testing, Open box testing, Transparent box testing,
Code-based testing, and Glass box testing.

8. BLACK BOX TESTING :


---------------------------
Black Box Testing is a software testing method in which the functionalities of
software applications are tested without having knowledge of internal code
structure,
implementation details and internal paths. Black Box Testing mainly focuses on
input and output of software applications and it is entirely based on
software requirements and specifications. It is also known as Behavioral Testing.

9. RE-TESTING :
-----------------
Retesting is a process to check specific test cases that are found with bug/s in
the final execution. Generally, testers find these bugs while testing
the software application and assign it to the developers to fix it. Then the
developers fix the bug/s and assign it back to the testers for verification.
This continuous process is called Retesting.

10. FUNCTIONAL TESTING :


------------------------------
Functional Testing is a type of software testing that validates the software system
against the functional requirements/specifications.
The purpose of Functional testing is to test each function of the software
application, by providing appropriate input, verifying the output against the
Functional requirements.

Functional testing mainly involves black box testing and it is not concerned about
the source code of the application.
This testing checks User Interface, APIs, Database, Security, Client/Server
communication and other functionality of the Application Under Test.
This test can be done either manually or using automation.

11. NON-FUNCTIONAL TESTING :


-------------------------------------
Non-Functional Testing is defined as a type of Software testing to check non-
functional aspects (performance, usability, reliability, etc) of a software
application.
It is designed to test the readiness of a system as per nonfunctional parameters
which are never addressed by functional testing.

12. USER ACCEPTANCE TESTING :


-------------------------------------
User Acceptance Testing (UAT) is a type of testing performed by the end user or the
client to verify/accept the software system before moving the software application
to the production environment. UAT is done in the final phase of testing after
functional, integration and system testing is done.

You might also like