Integration testing: Difference between revisions

Revision as of 15:01, 22 April 2019

Revision as of 12:12, 7 August 2019

Line 1:

{{RefimproveMore citations needed|date=August 2010}}

{{Software development process}}

'''Integration testing''' (sometimes called '''integration and testing''', abbreviated '''I&T''') is the phase in [[software testing]] in which individual software modules are combined and tested as a group. Integration testing is conducted to evaluate the [[regulatory compliance|compliance]] of a system or component with specified [[functional requirement]]s.<ref>{{Cite book|title=ISO/IEC/IEEE International Standard - Systems and software engineering|last=|first=|publisher=ISO/IEC/IEEE 24765:2010(E)|year=2010|isbn=|___location=|pages=vol., no., pp.1-4181–418, 15 Dec. 2010}}</ref> It occurs after [[unit testing]] and before [[Software verification and validation|validation testing]]. Integration testing takes as its input [[module (programming)|modules]] that have been unit tested, groups them in larger aggregates, applies tests defined in an integration [[test plan]] to those aggregates, and delivers as its output the integrated system ready for [[system testing]].<ref>[https://books.google.com/books?id=utFCImZOTEIC&pg=PA73&dq=integration+test&hl=en&sa=X&ei=4EpTVOvJMayu7Aak5YCIDA&ved=0CDwQ6AEwAg#v=onepage&q=integration%20test&f=false Martyn A Ould & Charles Unwin (ed), ''Testing in Software Development'', BCS (1986), p71]. Accessed 31 Oct 2014</ref>

== Approach ==

Line 22:

==See also==

{{Portal|Software Testing}}

* [[Design predicates]]