EnjoySharePoint YouTube Channel

Top-Down and Bottom-up Approach in Integration Testing

While doing Integration testing we are following Top-down and Bottom-up approach.

Get Office 365 Enterprise E3 Or Business Premium Subscription & Try out all the features

Also check out my previous posts on Performance Testing, Tips For test case design and Bug Life Cycle.

Top-Down Approach:-
Integration of the main module with some of the stub modules is called as a Top-down approach. In this case, we are using temporary programs instead of under constructive Stub modules. By doing this we can stop the control to the module which is under construction.

Bottom-Up Approach:-
Integration of sub-modules without main module is called as a Bottom-Up approach. In this case, instead of the main module, we are using a temporary program called a driver. Here we are using driver to send the control or to connect to the next module.

Also, you can check my previous posts on:

– The RPC server is an unavailable error in SharePoint 2016

– Add web part zone using SharePoint designer 2010

– Create an event handler to prevent items from deleting an item from SharePoint list using Visual Studio 2010

Check out Best Alternative to InfoPath -> Try Now
You May Also like the Following SharePoint Tutorials:

About Bijay Kumar

I am Bijay from Odisha, India. Currently working in my own venture TSInfo Technologies in Bangalore, India. I am Microsoft Office Servers and Services (SharePoint) MVP (5 times). I works in SharePoint 2016/2013/2010, SharePoint Online Office 365 etc. Check out My MVP Profile.. I also run popular SharePoint web site SharePointSky.com

View all posts by Bijay Kumar →