Types of Testing

Testing can be categorized into two types

I. Functional Testing
II.Non-Functional Testing
Types of Functional Testing:
1.Smoke Testing:
It’s just like initial testing. To check whether the
project will run or not. In smoke testing a subset of
testcase that cover the main functionality of the
system are selected and run to ensure that the most
crucial functions of program works correctly.
Purpose:
To determine whether the application is badly
broken that further testing is unnecessary.

2.sanity Testing:

Testing the modules in depth.

In other words: A sanity test is a very brief run-
through of the functionality of a computer program,
system, calculation, or other analysis, to assure that
the system or methodology works as expected, often
prior to a more exhaustive round of testing.
It determines whether it is reasonable to proceed
with further testing.
If the smoke test fail it is impossible to conduct
sanity testing.
Retesting:

Re-running the failed testcases.It means testing

the bug again once the coding is fixed to ensure that
all are working fine.

Regression testing:

The intent of regression testing is to assure that a

change, such as a bugfix, did not introduce new
bugs.
Testing some other testcase functionality to ensure
the above code fix haven’t introduced any problem
to existing code/functionality which was working
fine earlier.
Random Testing:

It is useful when the time needed to write and

directed test is too long or it is impossible to test
every combination.
In simple, we say without any sequence randomly
we will do testing.

Database Testing:

Testing the code for database,to check whether the

datas are stored and retrieve properly ,check data
validity and data integrity.

Data validity- Testing whether the front end data is

correctly added into the database.

Data Integrity- Testing Whether the front end

operations are correctly done on the back end data.
Adhoc Testing:

Adhoc testing is performed without planning and

documentation.
Test are intended to be run only once unless a defect
is discovered.

Monkey Testing:

While Testing – jumping from one module to

another module.

In other Words: Due to lack of time testing team is

conducting the test on specific area (or) basic
functionalities (or) main modules of our application.
Batch testing:
Sequential execution of more than one testcase.

Every test batch consists of multiple dependent

testcase. In these batches every end state is base to
next case.
Vertical Testing:

When complete set of functionality is taken for one

module and tested it is called vertical testing.

Horizontal Testing:

When a similar function is taken across all modules

and tested in horizontal testing.

Globalization:

In Globalized product , code is separated from the

message or text that it uses.this enable software to be
used with different languages without having to
rebuild the complete software.

Localization:

Process of adapting the internationalized software

for a specific region or language by adding locale
specific components and translating the text.
Non-Functional Testing:

Performance Testing:

It is the process of determining the speed or

effectiveness of a computer ,network,software
program or device. Testing the efficiency of the
system.

1. Load Test – Maximum number of inputs that the

system can handle.Its a performance testing to
check system behavior under load, such as testing of
a web site under a range of loads to determine at
what point the system’s response time degrades or
fails.

2. Stress Test – Maximum load beyond the tolerance

level.system is stressed beyond its specifications to
check how and when it fails. performed under heavy
load like putting large number beyond storage
capacity , complex database queries, continuous
input to system or database load. Stressing the
system at or beyond the limit is called stress testing.
3.volume Test- The purpose of volume is to find the
weakness in the system with respect to its handling
of large amount of data during short time period.
Example:
This kind of testing ensures that the system
will process data across physical and logical
boundaries such as across servers and across disk
partition on one server.

Usability Testing:

Determines how well the user will be able to

understand and interact with the system. It means
how the application runs on user friendly.
In this the application flow is tested ,can new user
understand the application easily,proper help
document whenever user stuck at any point.
Basically system navigation is checked in this
testing.

Security Testing:
 Testing which confirms that the program can
restrict access to authorized personal and authorized
personnel can access the functions available to their
security level.
Example:
If your site requires firewalls ,encryption ,user
authentication,financial transaction, or access to
database with sensitive data, you may need to test
these and also test your site’s overall protection
against unauthorized internal or external access.

Configuration testing:

Testing the compatibility of hardware and

software. Testing the supporting software platform.

It checks how an application works in different

configuration environments (OSs, DBMS,
peripherals, mobile carriers, network capacity,
hardware, etc.).

Recovery Testing:
 Testing how well systems recovers from expected or
unexpected events without loss of data or
functionality. When an application fails or crashes,
there is always a possibility of data lost.
Getting back the lost data in recovery testing.

Hard kill-check in hardware(i.e. removing the RAM

& check whether data is lost or recovered)

Soft kill-
Ending the application in between & check whether
the application is lost(e.g. MS-Word)

Scalability Testing:

Testing the ability of a network, a process to

continue to function well when it is changed in size
or volume in order to meet a growing need.

Example:
When the software is released , the number of
users accessing the application may be limited.
when the business grows , the need for more users
to access the software also increased and so, more
users will be given access to the software. Without
affecting the existing software, new hardware may
be added to accommodate the business volume.

Scalability point:

The point at which application gets crashed.

Alpha Testing:

Alpha testing is where both the customers and tester

will validate the product in the same place.

Testing of a software product or system conducted at

the developer's site by the end user.

Beta Testing:

Before the entire product is completed, the company

will release the product called the BETA version. So
that the client will test the product and he will find
the defects.

Pre-Beta Testing:
 Testing the application with the closure client.
Ex: Employee of Microsoft product.

Online Testing:

In specific application only we will do the testing and

immediate testing
Ex: banking application, online ticket reservation.
Bench Mark Testing:
We will compare our application with other
competitor .
MutationTesting:

Deliberately insert the bug and checks that how fast

affecting the application.
Endurance Testing:

To test the application in long duration. (2-3 days)