English Deutsch Français Italiano Español Português 繁體中文 Bahasa Indonesia Tiếng Việt ภาษาไทย
All categories

5 answers

Integration testing is when you are testing various components - modules that are being called from one component etc. This is where stubs and drivers are used. The approach is a Top-Down or a Bottom-Up testing and Sandwich testing.

E.g a menu driven component calls another module, this requires integration.

System testing comprises of Testing for performance. e.g. Load Testing, Volume Testing, Compatibility Testing etc.


If you require to understand be certified as a Tester - for easy availability of jobs, you can complete your certification from an institute like STQC. www.stqc.nic.in

2006-10-17 20:00:43 · answer #1 · answered by indiangal 3 · 0 0

Integration testing is the type of testing done when two or more modules of a particular software are merged. it is to see whether the code in one module affects the other module.
initially, there will be a common code. There may be 2 or more requirements. So, the requirements may be assigned to more than one person to work on. So, they take the common code and work on it. So, when everyone finishes the job, all the code has to be integrated and tested whether change in one module affects the other. This is integration testing.

While System testing is done after the integration testing. It is like testing whether the developed software satisfies the requirements and whether it works fine without any problem. System testing is also done to check whether the software is compatible to be run on that particular hardware. They run the software in different configuration systems and see which hardware is compatible.

2006-10-17 20:03:34 · answer #2 · answered by Pandian 3 · 0 0

Hi shraddha k,

i think you know abt all types of testing. First i will let you know the types of testing and then explain abt it.

1. Unit Testing
2. Module Testing
3. Integration Testing
4. System Testing
5. Alpha Testing
and Beta

Now coming to ur doubt.....

Consider there are many modules developed for a particular software.....by different persons.

When 2 or more persons combine their module with others and test the functionality then it is called as Integration Testing since they are integrating their modules.

when they install their program in a realtime system and test it for the performance and other details then it is called as system testing.......

Hope this helps you.....

Please mail me if you have more doubts....
venkatesh_varalu@yahoo.co.in

2006-10-17 20:02:12 · answer #3 · answered by Anonymous · 0 0

Integration testing

Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems.

System Testing

Testing that attempts to discover defects that are properties of the entire system rather than of its individual components

2006-10-17 22:21:10 · answer #4 · answered by Anonymous · 0 0

"System testing" is a high level testing and "integration testing" is a lower level testing. Integration testing is completed first, not system testing. In other words, upon completion of integration testing, system testing is started, not vice versa.

For integration testing, test cases are developed with the express purpose of exercising the interfaces between the compoments. For system testing is configured in controlled environment, and test cases are developed to simulate real life scenarious that occur in a simulated real life test environment.

The purpose of integration testing is to ensure distinct components of the application still work in accordance to customer requirements. The purpose system testing is to validate an application's accuracy and completeness in performing the functions as designed, and to test all functions of the system that are required in real life.

2006-10-17 20:57:44 · answer #5 · answered by Anonymous · 1 0

fedest.com, questions and answers