766:
790:
778:
754:
740:
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.
25:
735:
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
739:
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
746:
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.
732:. Other Integration Patterns are: collaboration integration, backbone integration, layer integration, client-server integration, distributed services integration and high-frequency integration.
655:
609:
736:
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.
576:
743:
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.
904:
648:
418:
566:
641:
541:
282:
561:
42:
599:
508:
272:
874:
375:
108:
89:
1154:
498:
493:
249:
61:
627:
897:
518:
231:
211:
46:
68:
729:
428:
317:
307:
257:
1179:
1118:
604:
332:
297:
148:
423:
395:
849:
75:
546:
390:
277:
267:
206:
35:
1215:
1210:
1123:
890:
312:
292:
57:
1164:
1113:
1083:
1025:
453:
322:
302:
765:
789:
581:
463:
342:
216:
816:
777:
753:
706:
523:
433:
385:
327:
1043:
1038:
702:
380:
347:
163:
153:
716:
that have been unit tested, groups them in larger aggregates, applies tests defined in an integration
1088:
1078:
713:
690:
Integration testing describes tests that are run at the integration-level to contrast testing at the
443:
287:
221:
188:
168:
129:
1073:
1068:
1058:
947:
937:
438:
357:
183:
1128:
1103:
1063:
1053:
997:
811:
556:
82:
1138:
964:
932:
927:
870:
806:
1108:
1093:
1048:
974:
959:
952:
913:
680:
513:
476:
458:
448:
173:
728:
Some different types of integration testing are big-bang, mixed (sandwich), risky-hardest,
1133:
684:
400:
352:
236:
158:
1184:
1159:
1098:
1007:
979:
695:
1204:
143:
1174:
1169:
1012:
942:
691:
226:
1189:
1033:
969:
24:
839:. ISO/IEC/IEEE 24765:2010(E). 2010. pp. vol., no., pp.1–418, 15 Dec. 2010.
717:
712:
In a structured development process, integration testing takes as its input
178:
720:, and delivers as output test results as a step leading to system testing.
551:
503:
488:
483:
837:
ISO/IEC/IEEE International
Standard - Systems and software engineering
262:
882:
337:
571:
886:
18:
867:
Testing Object-Oriented
Systems: Models, Patterns, and Tools
701:
Often, integration testing is conducted to evaluate the
1147:
1021:
990:
920:
49:. Unsourced material may be challenged and removed.
898:
649:
8:
905:
891:
883:
656:
642:
120:
109:Learn how and when to remove this message
850:Martyn A Ould & Charles Unwin (ed),
828:
749:
128:
610:Electrical and electronics engineering
7:
47:adding citations to reliable sources
14:
536:Standards and bodies of knowledge
1155:Graphical user interface testing
788:
776:
764:
752:
23:
852:Testing in Software Development
628:Outline of software development
34:needs additional citations for
1:
683:in which multiple parts of a
1180:Software reliability testing
1119:Software performance testing
1232:
1022:Testing types, techniques,
391:Software quality assurance
1165:Orthogonal array testing
1114:Smoke testing (software)
1084:Dynamic program analysis
687:are tested as a group.
376:Configuration management
16:Type of software testing
869:. Addison Wesley 1999.
730:top-down, and bottom-up
707:functional requirements
673:integration and testing
600:Artificial intelligence
856:. Accessed 31 Oct 2014
817:Continuous integration
524:Infrastructure as code
370:Supporting disciplines
1044:Compatibility testing
381:Deployment management
58:"Integration testing"
1089:Installation testing
1079:Differential testing
705:of a component with
201:Paradigms and models
130:Software development
43:improve this article
1074:Development testing
1069:Destructive testing
1059:Conformance testing
1003:Integration testing
948:Model-based testing
938:Exploratory testing
865:Binder, Robert V.:
669:Integration testing
124:Part of a series on
1129:Symbolic execution
1104:Regression testing
1064:Continuous testing
1054:Concurrent testing
998:Acceptance testing
921:The "box" approach
812:Functional testing
771:Bottom-up approach
519:Release automation
396:Project management
1198:
1197:
1139:Usability testing
965:White-box testing
933:All-pairs testing
928:Black-box testing
854:, BCS (1986), p71
807:Design predicates
795:Big bang approach
783:Sandwich approach
759:Top-down approach
666:
665:
557:ISO/IEC standards
119:
118:
111:
93:
1223:
1216:Hardware testing
1211:Software testing
1109:Security testing
1094:Negative testing
1049:Concolic testing
975:Mutation testing
960:Grey-box testing
953:Scenario testing
914:Software testing
907:
900:
893:
884:
877:
863:
857:
847:
841:
840:
833:
792:
780:
768:
756:
681:software testing
658:
651:
644:
605:Computer science
514:Build automation
121:
114:
107:
103:
100:
94:
92:
51:
27:
19:
1231:
1230:
1226:
1225:
1224:
1222:
1221:
1220:
1201:
1200:
1199:
1194:
1143:
1134:Test automation
1023:
1017:
986:
916:
911:
881:
880:
864:
860:
848:
844:
835:
834:
830:
825:
803:
796:
793:
784:
781:
772:
769:
760:
757:
726:
685:software system
679:, is a form of
662:
633:
632:
623:
615:
614:
595:
587:
586:
537:
529:
528:
479:
469:
468:
414:
406:
405:
401:User experience
371:
363:
362:
253:
242:
241:
202:
194:
193:
139:
138:Core activities
115:
104:
98:
95:
52:
50:
40:
28:
17:
12:
11:
5:
1229:
1227:
1219:
1218:
1213:
1203:
1202:
1196:
1195:
1193:
1192:
1187:
1185:Stress testing
1182:
1177:
1172:
1167:
1162:
1160:Manual testing
1157:
1151:
1149:
1145:
1144:
1142:
1141:
1136:
1131:
1126:
1124:Stress testing
1121:
1116:
1111:
1106:
1101:
1099:Random testing
1096:
1091:
1086:
1081:
1076:
1071:
1066:
1061:
1056:
1051:
1046:
1041:
1036:
1030:
1028:
1019:
1018:
1016:
1015:
1010:
1008:System testing
1005:
1000:
994:
992:
991:Testing levels
988:
987:
985:
984:
983:
982:
980:Static testing
977:
972:
962:
957:
956:
955:
950:
945:
940:
935:
924:
922:
918:
917:
912:
910:
909:
902:
895:
887:
879:
878:
858:
842:
827:
826:
824:
821:
820:
819:
814:
809:
802:
799:
798:
797:
794:
787:
785:
782:
775:
773:
770:
763:
761:
758:
751:
725:
722:
675:, abbreviated
671:, also called
664:
663:
661:
660:
653:
646:
638:
635:
634:
631:
630:
624:
621:
620:
617:
616:
613:
612:
607:
602:
596:
593:
592:
589:
588:
585:
584:
579:
574:
569:
564:
559:
554:
549:
547:IEEE standards
544:
538:
535:
534:
531:
530:
527:
526:
521:
516:
511:
506:
501:
496:
491:
486:
480:
475:
474:
471:
470:
467:
466:
461:
456:
451:
446:
441:
436:
431:
426:
421:
415:
412:
411:
408:
407:
404:
403:
398:
393:
388:
383:
378:
372:
369:
368:
365:
364:
361:
360:
355:
350:
345:
340:
335:
330:
325:
320:
315:
310:
305:
300:
295:
290:
285:
280:
275:
270:
265:
260:
254:
252:and frameworks
248:
247:
244:
243:
240:
239:
234:
229:
224:
219:
214:
209:
203:
200:
199:
196:
195:
192:
191:
186:
181:
176:
171:
166:
161:
156:
151:
146:
140:
137:
136:
133:
132:
126:
125:
117:
116:
31:
29:
22:
15:
13:
10:
9:
6:
4:
3:
2:
1228:
1217:
1214:
1212:
1209:
1208:
1206:
1191:
1188:
1186:
1183:
1181:
1178:
1176:
1173:
1171:
1168:
1166:
1163:
1161:
1158:
1156:
1153:
1152:
1150:
1146:
1140:
1137:
1135:
1132:
1130:
1127:
1125:
1122:
1120:
1117:
1115:
1112:
1110:
1107:
1105:
1102:
1100:
1097:
1095:
1092:
1090:
1087:
1085:
1082:
1080:
1077:
1075:
1072:
1070:
1067:
1065:
1062:
1060:
1057:
1055:
1052:
1050:
1047:
1045:
1042:
1040:
1037:
1035:
1032:
1031:
1029:
1027:
1020:
1014:
1011:
1009:
1006:
1004:
1001:
999:
996:
995:
993:
989:
981:
978:
976:
973:
971:
968:
967:
966:
963:
961:
958:
954:
951:
949:
946:
944:
941:
939:
936:
934:
931:
930:
929:
926:
925:
923:
919:
915:
908:
903:
901:
896:
894:
889:
888:
885:
876:
875:0-201-80938-9
872:
868:
862:
859:
855:
853:
846:
843:
838:
832:
829:
822:
818:
815:
813:
810:
808:
805:
804:
800:
791:
786:
779:
774:
767:
762:
755:
750:
748:
744:
741:
737:
733:
731:
723:
721:
719:
715:
710:
708:
704:
699:
697:
693:
688:
686:
682:
678:
674:
670:
659:
654:
652:
647:
645:
640:
639:
637:
636:
629:
626:
625:
619:
618:
611:
608:
606:
603:
601:
598:
597:
591:
590:
583:
580:
578:
575:
573:
570:
568:
565:
563:
560:
558:
555:
553:
550:
548:
545:
543:
540:
539:
533:
532:
525:
522:
520:
517:
515:
512:
510:
507:
505:
502:
500:
497:
495:
492:
490:
487:
485:
482:
481:
478:
473:
472:
465:
462:
460:
457:
455:
452:
450:
447:
445:
442:
440:
437:
435:
432:
430:
427:
425:
422:
420:
417:
416:
410:
409:
402:
399:
397:
394:
392:
389:
387:
386:Documentation
384:
382:
379:
377:
374:
373:
367:
366:
359:
356:
354:
351:
349:
346:
344:
341:
339:
336:
334:
331:
329:
326:
324:
321:
319:
316:
314:
311:
309:
306:
304:
301:
299:
296:
294:
291:
289:
286:
284:
281:
279:
276:
274:
271:
269:
266:
264:
261:
259:
256:
255:
251:
250:Methodologies
246:
245:
238:
235:
233:
230:
228:
225:
223:
220:
218:
215:
213:
210:
208:
205:
204:
198:
197:
190:
187:
185:
182:
180:
177:
175:
172:
170:
167:
165:
162:
160:
157:
155:
152:
150:
147:
145:
144:Data modeling
142:
141:
135:
134:
131:
127:
123:
122:
113:
110:
102:
91:
88:
84:
81:
77:
74:
70:
67:
63:
60: –
59:
55:
54:Find sources:
48:
44:
38:
37:
32:This article
30:
26:
21:
20:
1175:Soak testing
1170:Pair testing
1013:Unit testing
1002:
943:Fuzz testing
866:
861:
851:
845:
836:
831:
745:
742:
738:
734:
727:
711:
700:
689:
676:
672:
668:
667:
504:UML Modeling
499:GUI designer
164:Construction
154:Requirements
105:
96:
86:
79:
72:
65:
53:
41:Please help
36:verification
33:
1190:Web testing
1034:A/B testing
970:API testing
222:Prototyping
217:Incremental
189:Maintenance
169:Engineering
99:August 2010
1205:Categories
823:References
703:compliance
594:Glossaries
184:Deployment
69:newspapers
1039:Benchmark
718:test plan
413:Practices
237:Waterfall
212:Cleanroom
179:Debugging
149:Processes
1148:See also
801:See also
724:Approach
622:Outlines
552:ISO 9001
494:Profiler
489:Debugger
484:Compiler
459:Stand-up
1026:tactics
714:modules
698:level.
677:I&T
293:Lean SD
232:V model
174:Testing
83:scholar
873:
696:system
567:SWEBOK
288:Kanban
263:DevOps
227:Spiral
159:Design
85:
78:
71:
64:
56:
562:PMBOK
477:Tools
338:SEMAT
333:Scrum
207:Agile
90:JSTOR
76:books
1024:and
871:ISBN
692:unit
577:IREB
572:ITIL
542:CMMI
419:ATDD
328:SAFe
298:LeSS
273:DSDM
62:news
709:.
694:or
582:OMG
509:IDE
464:TDD
454:SBE
444:DDD
429:CCO
424:BDD
348:TSP
343:TDD
323:RUP
318:RAD
313:PSP
308:MSF
303:MDD
283:IID
278:FDD
268:DAD
258:ASD
45:by
1207::
449:PP
439:CD
434:CI
358:XP
353:UP
906:e
899:t
892:v
657:e
650:t
643:v
112:)
106:(
101:)
97:(
87:·
80:·
73:·
66:·
39:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
