Compatibility testing:

It is done to ensure that software works consistently with different

infrastructure components. Infra-structure parameters could be software,
hardware or other components.
- Processor
- Architecture (32 bit, 64 bit)
- Resource availability (Ram size)
- Equipment that the product is expected to work with (Printers, routers,
modems)
- OS and OS system services (FTP, DNS, …)
- Middle tier infrastructure components (Web server, appn server, network
server)
- Back end components
- Services that require special hardware cum software solutions (RAID
array, load balancing)
- Any software used to generate product binaries (compiler, linker ,..)
- Various technological components used to generate components (JDK,
SKD,…)
A compatibility matrix is created. A sample compatibility matrix for a mail
application is shown below:

Server Appn Web Client Browser MS Mail

server server office serve
r

Window Windows IIS Win2k IE 6.0 & Office Exchan

s 2000 2000 Adv 5.0 profession IE 5.5 2k & ge 5.5
Adv Server al & win 2k SP2 office & 2k
Server with SP4 Terminal XP
with SP4 & .Net server
MS sql framewor
server k 1.1
2000
with
SP3A
 Techniques :
1. Horizontal Combination:
Each feature of the product has to be tested with each row in the
Compatibility matrix
2. Intelligent sampling
The selection of intelligent samples is based on information
collected on the set of dependencies of the product with the
parameters.
3. Backward compatibility testing
It ensures that the current version of the product continues to
work with the older versions of the same product.
4. Forward compatibility testing
It is done to ensure that the product work with later versions of the
product (‘ex. IPV4 & IP V6).

User Documentation Testing:

It covers all the manuals, user guides, installation guides, set up
guides, read me file, software notes and online help that are provided with the
software to help the end user to understand the software system.

objectives:
1. To check if what is stated in the doc is available in the product
2. To check if what is there in the product is explained correctly in the
document.
Disadvantages:
1. It helps in highlighting problems
2. Results in less difficult support calls
3. New employees can use the documentation to learn the functionality of
the product
4. Customers need less training
Domain Testing:
In this testing, we do not look at the specifications of a software product but
we test the product based on domain knowledge and expertise in the
domain of application.
We need to know the day-to-day business activities for which the
software is written. It can be considered as an extension of black box
testing.
To design test case we need experts. It is easier to hire testers from the
domain area and train them in the software. It reduces the effort and time
required for training the testers.
Test cases are written based on what the users of the software do on a
typical day.
When you are testing as an end user in domain testing, all you are
concerned with is whether you got the right amount or not. Most of the
intermediate steps are missing. These “Missing steps” are expected to be
working before the start of domain testing.
Domain testing is done after all components are integrated and after the
product has been tested using other black box approaches.