What are the diff types of integration testing?
- 3 Answers
- 7531 Views
- Tech Mahindra, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / bhanu
Big Bang
In this approach, all or 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. The Big Bang 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.
A type of Big Bang Integration testing is called Usage Model testing. Usage Model testing can be used in both software and hardware integration testing. The basis behind this type of integration testing is to run user-like workloads in integrated user-like environments. In doing the testing in this manner, the environment is proofed, while the individual components are proofed indirectly through their use. Usage Model testing takes an optimistic approach to testing, because it expects to have few problems with the individual components. The strategy relies heavily on the component developers to do the isolated unit testing for their product. The goal of the strategy is to avoid redoing the testing done by the developers, and instead flesh out problems caused by the interaction of the components in the environment. For integration testing, Usage Model testing can be more efficient and provides better test coverage than traditional focused functional integration testing. To be more efficient and accurate, care must be used in defining the user-like workloads for creating realistic scenarios in exercising the environment. This gives that the integrated environment will work as expected for the target customers.
[edit]Top-down and Bottom-up
Main article: Top-down and bottom-up design
Bottom Up Testing is an approach to integrated testing where the lowest level components are tested first, 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.
Top Down Testing is an approach to integrated testing where the top integrated modules are tested and the branch of the module is tested step by step until the end of the related module.
Sandwich Testing is an approach to combine top down testing with bottom up testing.
The main advantage of the Bottom-Up approach is that bugs are more easily found. With Top-Down, it is easier to find a missing branch link.
| Is This Answer Correct ? | 2 Yes | 1 No |
Any one send me sample question for multimedia testing with microsoft access database. I am having interview next week. Please post it or send me my personal e-mail. Thank You
what is your current team size?
What r the roles and responsibilities of a TestLead?
How would you define a "bug?"
what is the difference between regression testing and re testing..?
write testcases for open dialogbox
What is the initial stage of testing?
What are the non functional requirements?
What is smoke testing and when it will be done?
Difference between or when do you conduct Acceptance testing User Interface testing ?
Whatis the need of writing testcases? why don,t test the application without the testcases
IS this a right Product.? Is this Product right.? Which of the above statement stands for Verfication and validation.?
Automation Testing 
