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