Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Integration testing
open-in-new
<h2 id="approach">Approach</h2> <p>Some different types of integration testing are big-bang, mixed (sandwich), risky-hardest, <a href="/facts/Top-down_and_bottom-up_design/MvtTkA3x">top-down, and bottom-up</a>. Other Integration Patterns<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> are: collaboration integration, backbone integration, layer integration, client-server integration, distributed services integration and high-frequency integration. </p><p>In big-bang testing, most of the developed modules are coupled together to form a complete software system or major part of the system and then used for integration testing. This method is very effective for saving time in the integration testing process . However, if the test cases and their results are not recorded properly, the entire integration process will be more complicated and may prevent the testing team from achieving the goal of integration testing. </p><p>In bottom-up testing, the lowest level components are tested first, and are then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested. All the bottom or low-level modules, procedures or functions are integrated and then tested. After the integration testing of lower level integrated modules, the next level of modules will be formed and can be used for integration testing. This approach is helpful only when all or most of the modules of the same development level are ready. This method also helps to determine the levels of software developed and makes it easier to report testing progress in the form of a percentage. </p><p>In top-down testing, the top integrated modules are tested first and the branch of the module is tested step by step until the end of the related module. </p><p>Sandwich testing combines top-down testing with bottom up testing. One limitation to this sort of testing is that any conditions not stated in specified integration tests, outside of the confirmation of the execution of design items, will generally not be tested. </p> <h2 id="see-also">See also</h2> <ul><li><a href="/facts/Design_predicates/l0qFoBVm">Design predicates</a></li> <li><a href="/facts/Functional_testing/2VudQTaz">Functional testing</a></li> <li><a href="/facts/Continuous_integration/M4RYgSzt">Continuous integration</a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>ISO/IEC/IEEE International Standard - Systems and software engineering. ISO/IEC/IEEE 24765:2010(E). 2010. pp. vol., no., pp.1–418, 15 Dec. 2010. <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>Martyn A Ould & Charles Unwin (ed), Testing in Software Development, BCS (1986), p71. Accessed 31 Oct 2014 <a href="https://books.google.com/books?id=utFCImZOTEIC&dq=integration+test&pg=PA73" target="_blank">https://books.google.com/books?id=utFCImZOTEIC&dq=integration+test&pg=PA73</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>Binder, Robert V.: Testing Object-Oriented Systems: Models, Patterns, and Tools. Addison Wesley 1999. ISBN 0-201-80938-9 <a href="/wiki/ISBN_(identifier)" target="_blank">/wiki/ISBN_(identifier)</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> </ol>