Integration Testing

Integration testing is a systematic technique for constructing the program structures, while conducting test to uncover errors associated with interfacing, the objective is to take unit tested modules and build a program structure that has been dictated by design.

User interface of i-Admit was developed in modules. All of them were joined together to make the complete running application. While integrating these modules, integration testing was performed on them to verify that they meet all interfacing requirements and that they pass relevant information among themselves. In the end the complete program structure was tested to ensure interoperability of all the modules.

Validation Testing

At the culmination of integration testing software is completely assembled as a package: interfacing errors have been uncovered and corrected and a final series of software tests –Validation Testing may begin. Validation can be defined in many ways, but a simple definition is that validation succeeds when software functions in a manner that can be reasonably expected by the customer. Software validation is achieved through a series of Black Box tests that demonstrate conformity with requirements.

Alpha Testing

It is virtually impossible for a software developer to foresee how the customer will really use a program. When custom software is built for one customer a series of acceptance tests are conducted to enable the customer to validate all requirements.

A customer conducts the alpha test at the developer site. The software is used in a natural setting with the developer “looking over the shoulder” of the user and recording errors and usage problem. Alpha tests are conducted in a controlled environment.

Alpha tests were performed at our development site with the help of our friends, who were called and asked to run the program in the manner they like, without our guidance and errors and usage problems were noted and code was updated to remove all of them.

Date: 2015-01-11; view: 954