Interested to Buy Any Domain ? << Click Here >> for more details...
How integration testing performed in organization
- 5 Answers
- 10628 Views
- Satyam, I also Faced
- E-Mail Answers
Answer Posted / anjani d
Integration Testing having two approaches,
Bottom up : stubs to Root
Top down : Root to stubs
Integration testing is a logical extension of unit testing.
In its simplest form, two units that have already been
tested are combined into a component and the interface
between them is tested. A component, in this sense, refers
to an integrated aggregate of more than one unit. In a
realistic scenario, many units are combined into components,
which are in turn aggregated into even larger parts of the
program. The idea is to test combinations of pieces and
eventually expand the process to test your modules with
those of other groups. Eventually all the modules making up
a process are tested together. Beyond that, if the program
is composed of more than one process, they should be tested
in pairs rather than all at once.
Integration testing identifies problems that occur when
units are combined. By using a test plan that requires you
to test each unit and ensure the viability of each before
combining units, you know that any errors discovered when
combining units are likely related to the interface between
units. This method reduces the number of possibilities to a
far simpler level of analysis.
You can do integration testing in a variety of ways but the
following are three common strategies:
* The top-down approach to integration testing requires
the highest-level modules be test and integrated first. This
allows high-level logic and data flow to be tested early in
the process and it tends to minimize the need for drivers.
However, the need for stubs complicates test management and
low-level utilities are tested relatively late in the
development cycle. Another disadvantage of top-down
integration testing is its poor support for early release of
limited functionality.
* The bottom-up approach requires the lowest-level units
be tested and integrated first. These units are frequently
referred to as utility modules. By using this approach,
utility modules are tested early in the development process
and the need for stubs is minimized. The downside, however,
is that the need for drivers complicates test management and
high-level logic and data flow are tested late. Like the
top-down approach, the bottom-up approach also provides poor
support for early release of limited functionality.
* The third approach, sometimes referred to as the
umbrella approach, requires testing along functional data
and control-flow paths. First, the inputs for functions are
integrated in the bottom-up pattern discussed above. The
outputs for each function are then integrated in the
top-down manner. The primary advantage of this approach is
the degree of support for early release of limited
functionality. It also helps minimize the need for stubs and
drivers. The potential weaknesses of this approach are
significant, however, in that it can be less systematic than
the other two approaches, leading to the need for more
regression testing.
| Is This Answer Correct ? | 2 Yes | 0 No |
Post New Answer View All Answers
When did u complete testing ? Which scenrio should not be in automation testing ? why ?
Hello. I am not here to answer your question. I jus found a job as software QA engr. And i am totally new to software testing. So can someone pls help me in the following scenario? there is this registration screen, and it contain: One textbox called Nickname which only accept alphanumerical One textbox called Contact which only accept numerical, One textbox called Email which can be filled with alphanumerical and symbol and One button called Register now becos there is so many textboxes, where i can filled with alphabet, number, symbol, "just space", leading zeros, leading space. there will be lots of combination. can someone pls help.. i will be appreciated if u can post the test case of the scenario i mentioned. Lots of Thanks
Explain some techniques for developing software components with respect to testability.
where can i learn domain knowledge? how cab i gain domain knowledge? what types of Questions can be asked in domain(BFSI)? PLZ REPLY ME
Hi there, I am new to the world of testing. Is there any place where I can have a look at an actual specification documents or test plans or test cases. This will help me in generating a level of confidence. Looking forward to your replies
what types of testing you performed in transfer funds module....
ive been looking for a junior tester job for quite some time now, but most company keep requisting for experienced staffs, but if i dont start from somewhere how do i get the experience
what are the test bugs
What is quality center? How many built in tables does quality center have?
What exactly is quality control?
What is Cyclometric testing?
what does 80hz refresh rate indicates?
hi friends i recently finished testing course in hyderabad.now am looking for a job in uk.i need help about the projects in interview point.can any one explain me abt banking project or credit card.like what are the problems faced in u r last project etc.
How would you test a service oriented architecture (soa) web application?
What is bug, deffect, issue, error?
