TESTING
TESTING LEVELS
Tests are frequently grouped by where they are
added in the software development process, or by the level of specificity of the test.
The main levels during the development process
are unit-, integration-, and system testing that are distinguished by the test target without
implying a specific process model.
Other test levels are classified by the testing
TEST LEVELS BY THE TESTING
OBJECTIVE
Acceptance/qualification testing; Installation testing;
Alpha and beta testing;
Conformance testing/Functional
testing/Correctness testing;
Regression testing; Performance testing; Stress testing;
Back-to-Back testing; Recovery testing;
ACCEPTANCE/QUALIFICATION
TESTING
Acceptance Testing is a test conducted to
determine if the requirements of a specification or contract are met.
Acceptance testing checks the system behavior
against the customer’s requirement.
These may have been expressed; the customers
undertake, or specify, typical tasks to check that their requirements have been met or that the
organization has identified these for the target market for the software.
This testing activity may or may not involve the
INSTALLATION TESTING
Installation testing is one of the most important part of
testing activities.
Installation is the first interaction of user with our
product and it is very important to make sure that user do not have any trouble in installing the software.
If installation fails then our program will not work on
that system not only this but can leave user’s system badly damaged.
Installation testing is a kind of quality assurance work
ALPHA AND BETA TESTING
Before the software is released, it is sometimes
given to a small, representative set of potential users for trial use, either in-house (alpha testing) or external (beta testing).
These users report problems with the product. Alpha and beta use is often uncontrolled, and is
CONFORMANCE
TESTING/FUNCTIONAL
TESTING/CORRECTNESS TESTING
Conformance testing is aimed at validating
whether or not the observed behavior of the tested software conforms to its specifications.
Conformance testing, also known as
REGRESSION TESTING
Regression testing is done to ensure that
enhancement, defect fixes or any other changes made to the software has not broken any existing functionality.
Regression testing is very important, because in
most places these days iterative development is used.
It make sense to have regression testing for every
PERFORMANCE TESTING
Performance testing is conducted after the
completion of functional testing.
Performance testing is usually conducted for web
applications.
Main objective of performance testing is to get
information with respect to response time,
throughput and utilization under a given load.
Performance testing is normally used with Load
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.
The idea is to create an environment more
demanding of the application than the
BACK-TO-BACK TESTING
A single test set is performed on two
implemented versions of a software product, and the results are compared.
Best example for Back to Back testing is testing
two versions of a component with same inputs and comparing the outputs.
The outputs are analyzed if there are any
RECOVERY TESTING
Recovery testing is the activity of testing how well
an application is able to recover from crashes, hardware failures and other similar problems.
Examples of recovery testing:
While an application is running, suddenly restart the
computer, and afterwards check the validness of the application's data integrity.
While an application is receiving data from a network,
CONFIGURATION TESTING
Configuration testing is the process of checking
USABILITY TESTING
This process evaluates:
how easy it is for end-users to use
and learn the software, including
user documentation;
how effectively the software
functions in supporting user tasks;
its ability to recover from user
QUESTIONS
What are the main testing levels during the
development process?
What are other levels?
What is the difference between alpha and beta
testing?