Types of Tests

Accessibility testing
Accessibility testing measures how well the sites interface accommodates
users with disabilities; part of this issue is the fact that specialized browsers
exist for disabled users (screen readers, Braille readers, etc.) which have trouble
rendering some HTML constructions in meaningful ways.
browser compatibility testing
Please see compatibility testing.
compatibility testing
Compatibility testing measures how well pages display on different clients; for
example: browsers, different browser version, different operating systems, and
different machines. At issue are the different implementations of HTML by the
various browser manufacturers and the different machine platform display and
rendering characteristics. Also called browser compatibility testing and crossbrowser testing.
component testing
cross-browser testing
Please see compatibility testing.
download testing
integration testing
Integration tests are performed when new code is added to an existing code
base; for example, when a new function is added to a set of existing functions.
Integration tests measure whether the new code works integrates with the
existing code; these tests look for data input and output, correct handling of
variables, etc.
modem testing
Please see download testing.
performance testing
Performance testing generally describes the processes of making the web site
and its server as efficient as possible, in terms of download speed, machine
resource usage, and server request handling.
production testing

regression testing
The term regression testing can be applied two ways. First, when a code
problem has been fixed, a regression test runs tests to verify that the defect is in
fact fixed; Imagine finding an error, fixing it, and repeating the test that
exposed the problem in the first place. This is a regresson test (Kaner
in Testing Computer Software). Second, regression testing is the counterpart
of integration testing: when new code is added to existing code, regression
testing verifies that the existing code continues to work correctly, whereas
integration testing verifies that the new code works as expected.
regression testing can describes the process of testing new code to verify that
this new code hasnt broken any old code.
security auditing
Security auditing refers to the testing of the site and web server configuration
with an eye towards eliminating any security or access loopholes.
smoke testing
stress testing
system stability testing
testability testing
Whenever a major change has been made to the code for a site like a new
code drop being installed on the server(s) somebody must sign off on the
installation or change as functioning correctly on a broad level. If the web
server itself is hosed, you cant test at any finer level of granularity.
unit testing
usability testing
Usability testing measures the sites interface for ease and intuitiveness of
navigation.
user acceptance testing
User acceptance testing refers to the process, between web site owners and
contractors, of setting up criteria for the formal acceptance of the web site code.
Somebody must define the tests that the web site code must meet in order for
the site work to be considered complete and somebody must execute those
acceptance tests.
user scenario testing
user testing

User tests are observational tests where a user or set of users are given tasks to
perform using some software or product
validation testing
Validation is the term for verifying that the HTML code in a file meets the DTD
(Document Type Definition) for any particular version of HTML. This is
important because strict adherence to a DTD specification ensures the best
likelihood of any file being fully supportable by a browser that follows that
DTD

For SAP applications the common testing

Unit Testing:
This part of testing is mostly taken care by the developers based on their
defined unit testing rules as per the organizations. This is sometimes done by
the skilful white box testers. The test is done in the development box. This is
the testing of interfaces, conversions, enhancement, reports, work flows and
forms(RICEWF) developed primarily with ABAP code. Testing of development
object includes testing for security authorization, ,data transfer rules,
reconciliations and batch scheduling jobs. BW (Business Warehouse) testing is
also part of the development tests.

2.

Integration Testing:
It is the testing of combined components of a SAP application to determine if
they function together correctly. It is typically done in the QA environment and
uses realistic test data.

3.

Regression Testing:
Regression testing is done to ensure that the new changes implemented do not
adversely affect the existing working code. SAP R/3 is a tightly integrated
system. A single stack update, OSS note, transport, configuration changes, new
development interfaces can have cascading and severe effect. Regression
Testing is usually executed using automation tool by the testing team.

4.

Performance Testing:

It is testing SAP applications to ensure that they will perform well under
expected workload. Performance testing encompasses load , volume & stress
testing to determine system bottlenecks. The aim of this testing is to enhance
robustness of SAP applications and helps deploy systems that can sustain high
load forecast, with zero post production performance issues. The testing
includes checking business processes that may cause stress, due to high
transaction or batch volumes. It is usually executed using automated tools &
involves collaboration of basis, database, infrastructure and test teams to
monitor test results.
5.

Functional Testing:
Functional testing ensures that your implementation of SAP meets your
business requirements. SAP is highly configurable system and could be easily
integrated with in-house applications or third party tools. Given this varied
configuration and complexity functional testing is a must. Functional testing
removes uncertainty over business use cases and brings quality. It includes
review of design documents and creating test artifacts including test
requirements, test scenario and test cases. Functional testing is usually done
by the testing team with a background in particular SAP module being tested.

6.

User Acceptance Testing (UAT):

7.

Security Testing:
To ensure the safety of SAP applications, security testing is performed. High
risk areas like sap-portal security, network security, operational security,
product security, access control and source code audit for security are tested.
This is usually involves the basis, database, infrastructure, development and
test teams.

8.

Portal Testing:
These techniques involve testing the SAP Portals on different browser and
checking business processes