In this type of testing, the software is tested for the functional requirements.
The tests are written in order to check if the application behaves as expected.
Stress Testing:
The application is tested against heavy load such as complex numerical values,
large number of inputs, large number of queries etc. which checks for the
stress/load the applications can withstand.
Load Testing:
The application is tested against heavy loads or inputs such as testing of web
sites in order to find out at what point the web-site/application fails or at
what point its performance degrades.
Ad-hoc Testing:
This type of testing is done without any formal Test Plan or Test Case creation.
Ad-hoc testing helps in deciding the scope and duration of the various other
testing and it also helps testers in learning the application prior starting
with any other testing.
Exploratory Testing:
This testing is similar to the ad-hoc testing and is done in order to
learn/explore the application.
Usability Testing:
This testing is also called as �Testing for User-Friendliness�. This testing is
done if User Interface of the application stands an important consideration and
needs to be specific for the specific type of user.
Smoke Testing:
This type of testing is also called sanity testing and is done in order to check
if the application is ready for further major testing and is working properly
without failing up to least expected level.
Recovery Testing:
Recovery testing is basically done in order to check how fast and better the
application can recover against any type of crash or hardware failure etc. Type
or extent of recovery is specified in the requirement specifications.
Volume Testing:
Volume testing is done against the efficiency of the application. Huge amount of
data is processed through the application (which is being tested) in order to
check the extreme limitations of the system.
