Interested to Buy Any Domain ? << Click Here >> for more details...
What are the diff types of integration testing?
- 3 Answers
- 9062 Views
- Tech Mahindra, I also Faced
- E-Mail Answers
Answer Posted / 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 |
Post New Answer View All Answers
tell me 5 new requirements in ur project? plz urgent
How will you determine when to stop testing?
whats main working for tester. and developer, and prject manager.
Once automated, what are the types of functionality provides the highest Return On Investment (ROI) to the company?
what is date field test case
Tell me about Agile scrum and what is your role in Scrum ?
Discuss what test metrics you feel are important to publish an organization?
Explain user acceptance testing.
diff b/w desktop based testing & web application testing
Can you do system testing at any stage of sdlc?
what do you mean by Develop test data through sourcing (or) handcrafting techniques
can any one post the format of tracebility martrix Plz...... Maid Id: sandhya.shyamala@yahoo.com
What is the difference between three tier and two tier application?
How do test documents in a project span across the software development lifecycle?
What are the various techniques in black box testing?
