Top-Down Integration Testing is an important type of Integration Testing. It comes into the picture when Top level components are built first in the software or those who call other components. Tester will evaluate component interfaces starting with the top level component. To represent it diagrammatically,
Component ‘A’ is the top most component and can call other components ‘B’, ‘C’ and ‘D’. It’s components will be tested first before testing the low-level components. Similarly, ‘D’ can call ‘G’ and ‘H’ components; ‘B’ can call ‘E’ and ‘C’ can call ‘F’.
The interactions of all the components must be tested and there may be a situation where the low-level components have not been created. In that case, a skeletal implementation of the lower component is created, called a stub. A stub is nothing but a dummy created to receive input and giving an output based on the input without performing any operation. It’s very important in the Top-Down Integration testing as all the components are not ready at once.
Top-Down Integration Testing
Top-Down Testing
Component ‘A’ is the top most component and can call other components ‘B’, ‘C’ and ‘D’. It’s components will be tested first before testing the low-level components. Similarly, ‘D’ can call ‘G’ and ‘H’ components; ‘B’ can call ‘E’ and ‘C’ can call ‘F’.
The interactions of all the components must be tested and there may be a situation where the low-level components have not been created. In that case, a skeletal implementation of the lower component is created, called a stub. A stub is nothing but a dummy created to receive input and giving an output based on the input without performing any operation. It’s very important in the Top-Down Integration testing as all the components are not ready at once.
Follow and Like us:
Top-Down Integration Testing
No comments:
Post a Comment