1) Unit testing tests the minimal software component, or module. Each unit (basic component) of the software is tested to verify that the detailed design for the unit has been correctly implemented.

In an object-oriented environment, this is usually at the class level, and the minimal unit tests include the constructors and destructors.

2) Integration testing exposes defects in the interfaces and interaction between integrated components (modules).

Progressively larger groups of tested software components corresponding to elements of the architectural design are integrated and tested until the software works as a system.

source site :

http://en.wikipedia.org/w iki/Beta_testing#Testing_metho ds

Answered by Ni .. , an ibibo Master, at 11:07 AM on July 13, 2008

1) Unit testing tests the minimal software component, or module. Each unit (basic component) of the software is tested to verify that the detailed design for the unit has been correctly implemented.

In an object-oriented environment, this is usually at the class level, and the minimal unit tests include the constructors and destructors.

2) Integration testing exposes defects in the interfaces and interaction between integrated components (modules).

Progressively larger groups of tested software components corresponding to elements of the architectural design are integrated and tested until the software works as a system.

source site :

http://en.wikipedia.org/w iki/Beta_testing#Testing_metho ds

Answered by .... ..... , an ibibo Master, at 5:34 AM on July 12, 2008

1) Unit testing tests the minimal software component, or module. Each unit (basic component) of the software is tested to verify that the detailed design for the unit has been correctly implemented.

In an object-oriented environment, this is usually at the class level, and the minimal unit tests include the constructors and destructors.

2) Integration testing exposes defects in the interfaces and interaction between integrated components (modules).

Progressively larger groups of tested software components corresponding to elements of the architectural design are integrated and tested until the software works as a system.

source site :

http://en.wikipedia.org/w iki/Beta_testing#Testing_metho ds

Answered by Raksha , an ibibo Master, at 9:25 AM on July 09, 2008

1) Unit testing tests the minimal software component, or module. Each unit (basic component) of the software is tested to verify that the detailed design for the unit has been correctly implemented.

In an object-oriented environment, this is usually at the class level, and the minimal unit tests include the constructors and destructors.

2) Integration testing exposes defects in the interfaces and interaction between integrated components (modules).

Progressively larger groups of tested software components corresponding to elements of the architectural design are integrated and tested until the software works as a system.

source site :

http://en.wikipedia.org/w iki/Beta_testing#Testing_metho ds

Answered by Yash , an ibibo Master, at 9:53 AM on July 02, 2008

Testing can be done on the following levels:

1) Unit testing tests the minimal software component, or module. Each unit (basic component) of the software is tested to verify that the detailed design for the unit has been correctly implemented.

In an object-oriented environment, this is usually at the class level, and the minimal unit tests include the constructors and destructors.

2) Integration testing exposes defects in the interfaces and interaction between integrated components (modules).

Progressively larger groups of tested software components corresponding to elements of the architectural design are integrated and tested until the software works as a system.

For more details , Please visit the source site :

http://en.wikipedia.org/w iki/B eta_testing#Testing_methods

Answered by Romi , an ibibo Master, at 8:29 PM on June 21, 2008

1) Unit testing tests the minimal software component, or module. Each unit (basic component) of the software is tested to verify that the detailed design for the unit has been correctly implemented.

In an object-oriented environment, this is usually at the class level, and the minimal unit tests include the constructors and destructors.

2) Integration testing exposes defects in the interfaces and interaction between integrated components (modules).

Progressively larger groups of tested software components corresponding to elements of the architectural design are integrated and tested until the software works as a system.

source site :

http://en.wikipedia.org/w iki/Beta_testing#Testing_metho ds

Answered by Madhurima , an ibibo Master, at 5:52 PM on June 18, 2008

well, Unit testing involves only those characteristics that are vital to the performance of the unit under test. This encourages developers to modify the source code without immediate concerns about how such changes might affect the functioning of other units or the program as a whole. Once all of the units in a program have been found to be working in the most efficient and error-free manner possible, larger components of the program can be evaluated by means of integration testing.

Unit testing can be time-consuming and tedious. It demands patience and thoroughness on the part of the development team. Rigorous documentation must be maintained. Unit testing must be done with an awareness that it may not be possible to test a unit for every input scenario that will occur when the program is run in a real-world environment.

Component testing-
The component tests are divided into two separate scripts that test both server and mailer components. You will be able to determine specific components installed on your host's server as well as seeing a list of available components. If you are not sure whether an e-mail component is setup or functioning properly, the test will notify you also.

Integration testing-
Integration testing, also known as integration and testing (I&T), is a software development process which program units are combined and tested as groups in multiple ways. In this context, a unit is defined as the smallest testable part of an application. Integration testing can expose problems with the interfaces among program components before trouble occurs in real-world program execution. Integration testing is a component of Extreme Programming (XP), a pragmatic method of software development that takes a meticulous approach to building a product by means of continual testing and revision.

Answered by Saurabh , an ibibo Master, at 7:41 AM on June 17, 2008

hi there

1) Unit testing tests the minimal software component, or module. Each unit (basic component) of the software is tested to verify that the detailed design for the unit has been correctly implemented.

In an object-oriented environment, this is usually at the class level, and the minimal unit tests include the constructors and destructors.

2) Integration testing exposes defects in the interfaces and interaction between integrated components (modules).

Progressively larger groups of tested software components corresponding to elements of the architectural design are integrated and tested until the software works as a system.

source site :

http://en.wikipedia.org/w iki/Beta_testing#Testing_metho ds

Answered by Reeta K , an ibibo Master, at 11:12 AM on June 16, 2008

Hi, Aryan Gusain
Unit testing helps to eliminate uncertainty in the units themselves and can be used in a bottom-up testing style approach. By testing the parts of a program first and then testing the sum of its parts, integration testing becomes much easier.

A heavily debated matter exists in assessing the need to perform manual integration testing. While an elaborate hierarchy of unit tests may seem to have achieved integration testing, this presents a false sense of confidence since integration testing evaluates many other objectives that can only be proven through the human factor. Some argue that given a sufficient variety of test automation systems, integration testing by a human test group is unnecessary. Realistically, the actual need will ultimately depend upon the characteristics of the product being developed and its intended uses. Additionally, the human or manual testing will greatly depend on the availability of resources in the organization.

Answered by Nz , an ibibo Master, at 3:13 AM on June 14, 2008

Unit testing-
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. Unit testing is often automated but it can also be done manually. This testing mode is a component of Extreme Programming (XP), a pragmatic method of software development that takes a meticulous approach to building a product by means of continual testing and revision.

Unit testing involves only those characteristics that are vital to the performance of the unit under test. This encourages developers to modify the source code without immediate concerns about how such changes might affect the functioning of other units or the program as a whole. Once all of the units in a program have been found to be working in the most efficient and error-free manner possible, larger components of the program can be evaluated by means of integration testing.

Unit testing can be time-consuming and tedious. It demands patience and thoroughness on the part of the development team. Rigorous documentation must be maintained. Unit testing must be done with an awareness that it may not be possible to test a unit for every input scenario that will occur when the program is run in a real-world environment.

Component testing-
The component tests are divided into two separate scripts that test both server and mailer components. You will be able to determine specific components installed on your host's server as well as seeing a list of available components. If you are not sure whether an e-mail component is setup or functioning properly, the test will notify you also.

Integration testing-
Integration testing, also known as integration and testing (I&T), is a software development process which program units are combined and tested as groups in multiple ways. In this context, a unit is defined as the smallest testable part of an application. Integration testing can expose problems with the interfaces among program components before trouble occurs in real-world program execution. Integration testing is a component of Extreme Programming (XP), a pragmatic method of software development that takes a meticulous approach to building a product by means of continual testing and revision.

There are two major ways of carrying out an integration test, called the bottom-up method and the top-down method. Bottom-up integration testing begins with unit testing, followed by tests of of progressively higher-level combinations of units called modules or builds. In top-down integration testing, the highest-level modules are tested first and progressively lower-level modules are tested after that. In a comprehensive software development environment, bottom-up testing is usually done first, followed by top-down testing. The process concludes with multiple tests of the complete application, preferably in scenarios designed to mimic those it will encounter in customers' computers, systems and networks.

Answered by Anju Singh , an ibibo Master, at 8:08 PM on June 13, 2008