During the program development, computer programs and program modules are tested.

As the programs are integrated into the total information system, overall testing of the system is possible. When individual modules or programs are tested independently, it is called a unit testing. The various types of testing done on the system are Functional Testing Integration Testing Validation Testing Unit Testing

Functional Testing:

It is the systematic technique in which each and every module of the software system is tested and validated. Here each and every function performed by the system is tested. The main aim of this functional testing is to detect and correct errors in each and every module. Integration testing: Strategies for integrating software components into a functioning product include the Bottom-Up Top-Down Sandwich strategies

Integration testing was done to verify the co-existence of the modules and the forms involved bottom-up integration testing was used for this purpose.

After unit testing of the module they are integrated from the BottomUp combining each of the into clusters. Dummy driver modules are added to simulate the upper level and the clusters were tested Finally, when all of the modules were developed and integrated they were tested with the live data supplied by the user.

Bottom-Up Integration: Bottom-Up integration consists of Unit testing followed by testing of the entire system. Unit testing is the goal of discovering errors in the individual modules of the system. The primary purpose of the subsystem is to vary operation of the interface between the modules in the subsystem. Top-Down Integration: Top-Down integration starts with the main routine and one or two immediately subordinate routines in the system structure. Top-Down integration requires the use of program stubs to simulate the effect of lower level routing that are called by being tested. Sandwich strategies: Sandwich is predominately Top-Down but Bottom-Up techniques are used on some modules and subsystem. This solves many of the problems encountered in pure Top-Down integration at the subsystem and system level. Validation Testing:

At the culmination of integration testing the software is completely assembled as a package. Validation testing can be defined in many ways, but a simple definition is that validations succeed when the software is designed in a manner that can be reasonably expected by the user. Unit Testing: Unit testing is goal of discovering errors in the individual modules of the system. The following where considered during the unit test. The module interface is tested to ensure the data information properly flows in and out of the unit under the test The local data structure is examined to ensure that the data stored temporarily maintains integrity through the unit lifetime. Boundary conditions are tested. All independent paths through the condition structure are excised to ensure that all statements in the module have been executed at least once. All handling paths are tested.