Integration testing
De Software testing
Concepts
Facts
- The main objective of integration testing is to verify if the individually tested units communicate accordingly when integrated together. <bib>vincenzi-etal:2007:slides</bib>, <bib>delamaro:slides:2009</bib>
- Integration testing must be performed because data can be lost at the unit's interface. <bib>vincenzi-etal:2007:slides</bib>, <bib>delamaro:slides:2009</bib>
- Integration testing must be performed because global variables can suffer undesirable interferences. <bib>vincenzi-etal:2007:slides</bib>, <bib>delamaro:slides:2009</bib>
- In object oriented testing, the integration unit is the method. <bib>vincenzi-etal:2007</bib>
- In object oriented testing, the integration unit is the class, cluster, components and subsystems. <bib>vincenzi-etal:2007:slides</bib>, <bib>perry-kaiser:1990</bib>, <bib>binder:1999</bib>
- In procedural testing, the integration unit is two or more procedures, and subsystems. <bib>vincenzi-etal:2007:slides</bib>
- In procedural paradigm, the integration testing is called inter-procedural. <bib>vincenzi-etal:2007</bib>
- In object-oriented paradigm, considering the method as the integration unit, there are three types of integration testing: inter-method, intra-class and inter-class. <bib>vincenzi-etal:2007</bib>, <bib>harrold-rothermel:1994</bib>
- In object-oriented paradigm, considering the class as the integration unit, the integration testing is called inter-class. <bib>vicenzi-etal:2007</bib>, <bib>perry-kaiser:1990</bib>, <bib>binder:1999</bib>