1.
Security testing
Testing of the authorized access to the application.
Definition:
Security testing is basically a type of software testing that’s done to check whether the application or
the product is secured or not. It checks to see if the application is vulnerable to attacks, if anyone hack
the system or login to the application without any authorization.
•It is a process to determine that an information system protects data and maintains functionality as
intended.
•The security testing is performed to check whether there is any information leakage in the sense
by encrypting the application.
•Software security is about making software behave in the presence of a malicious attack.
•The six basic security concepts that need to be covered by security testing are: confidentiality,
integrity, authentication, availability, authorization and non-repudiation.
2. Unit testing
Testing of application's code.
Definition:
Unit testing is a software development process in which the smallest testable parts of an application,
called units, are individually and independently scrutinized for proper operation. A unit test is an
automated piece of code that invokes a unit of work in the system and then checks a single assumption
about the behavior of that unit of work. A unit of work can span a single method, a whole class or
multiple classes working together to achieve one single logical purpose that can be verified. It requires
detailed knowledge of the internal program design and code.
3. Smoke testing
Testing of application's core functionality.
Definition:
Smoke testing, in the context of software development, is a series of test cases that are run before the
commencement of more rigorous tests. The goal of smoke testing is to verify that an application's main
features work properly. Smoke testing is a preliminary test which is used to catch the high-level
functional errors of an application. If the tests fail, then further testing of the application stops, and the
build is refused for additional testing until the build passes the smoke test.
4. Functional testing
Testing of application's functionality as per the specification.
Definition:
Functionality testing is performed to verify that a software application performs and functions correctly
according to design specifications. During functionality testing we check the core application functions,
text input and menu functions. Functional test tends to answer the questions like “can the user do this”
or “does this particular feature work”. This is typically described in a requirements specification or in a
functional specification. This type of testing ignores the internal parts and focus on the output is as per
requirement or not. Black-box type testing geared to functional requirements of an application.
5. Performance testing
Testing of application behavior under load.
Definition:
Performance testing, a non-functional testing technique performed to determine the system parameters
in terms of responsiveness and stability under various workload. Performance testing measures the
quality attributes of the system, such as scalability, reliability and resource usage. In Stress testing the
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.
6. Regression testing
Retesting of the system after changes.
Definition:
Regression testing is a type of software testing that seeks to uncover new software bugs, or regressions,
in existing functional and non-functional areas of a system after changes such as enhancements,
patches or configuration changes, have been made to them. Regression testing is the process of testing
changes to computer programs to make sure that the older programming still works with the new
changes.
7. Disaster recovery plan
Definition:
A disaster recovery plan is a documented process or set of procedures to recover and protect a business
IT infrastructure in the event of a disaster. Such plan, ordinarily documented in written form, specifies
procedures an organization is to follow in the event of a disaster. It is a comprehensive statement of
consistent actions to be taken before, during and after a disaster. The disaster could be natural,
environmental or man-made. Just as a disaster is an event that makes the continuation of normal
functions impossible, a disaster recovery plan consists of the precautions taken so that the effects of a
disaster will be minimized and the organization will be able to either maintain or quickly resume
mission-critical functions.