Interested to Buy Any Domain ? << Click Here >> for more details...
How integration testing performed in organization
- 5 Answers
- 10803 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
what is data guidelines
what are the status have in QC(Test Management Tool). and how you report?
Please explain me v-model clearly i want to know how it works and want to know how it use in real time on a project please tell me its urgent and important for me understand .Please tell me my mail id is Chiku_69@yahoo.in Thank u
anybody there with 3+ exp in software testing looking for change and like to work in bangalore fwd your resume to vinodhanandhan@gmail.com
hi this is satish can some one help me out by sending the maxium notes on client sesrver ,web server and company architechture project hirearchy and company hirearchy i will happy to recive the answers as early as possible
How can you define state tanstion testing aswell decesion testing with examples.how you can differ them too??
What is a ‘test plan’?
Assume a login page, and you have written 10 cases(say for example). How will you justify that these 10 testcase suffient for the login and how do you say this is 100% satisfies the need.
what is API 2.0?
How to write testcases for unread/read mails for gamil inbox? and what are the types of testing you do on them?
What is the difference between static testing and dynamic testing?
How to find that tools work well with your existing system?
Beyond the customary advantages of having a testing group, what are the benefits does a company receive from a well run, automated testing group?
3.if a questions asked as,what is the quality standards you are following? what i need to tell.
What is an audit report? Whom is it done by?
