| Topic :: |
Integration Testing |
|
Topic Submitted By :: User1 |
| |
Reply Posted By |
| |
|
Re: Integration Testing |
Reply # 1 |
To provide the relation between two or more modules those
are already cinstructed or under construction to check out
whether those are working or not.  |
Narsing |
| |
|
Re: Integration Testing |
Reply # 2 |
Combing the modules in the application after developing all
the modules and after conducting unit testing. During
integration testing we are combing the modules and test the
data flow between the modules generally it is conducted by
the developers those who are involved in developing the
modules  |
Narender Reddy |
| |
|
|
| |
| |
|
Re: Integration Testing |
Reply # 3 |
All individual unit are integrated and tested is called
integrated testing  |
Mukesh |
| |
|
Re: Integration Testing |
Reply # 4 |
Initially Unit testing is conducted i,e Verifying the logic
of a single program is called unit testing and also we can
call as testing a single program.Once Unit testing is
completed those tested units(program) are intergrated and
we call it as a module.Then those modules are tested to
validate that after integrating all the programs that
module is functioning properly or not and we also call this
as Component testing also.Once all the modules are tested
then those modules are again integrated,To check those
interconnections are working properly or not we conduct
integration testing.For Example in Gmail application
Sentitems,Inbox.... are different modules and developed
independently.After completely developing those modules we
will integrate them and conduct integration testing so that
it is functioning as expected or not, for this we will
approaches Such as TOP Down,Bottom up,Big Bang,Hybrid
approach.
If I am wrong please correct me.  |
Shiva |
| |
|
Re: Integration Testing |
Reply # 5 |
tulasi ravi kumar +91-9951123501
Combined/integrated all the modules and we test exact
navigation from module to another module.
The purpose of integration testing is to ensure distinct
components of the application still work in accordance to
customer requirements.  |
Ravi148 |
| |
|
Re: Integration Testing |
Reply # 6 |
all the elements(modules)are connected to each other and
after that we are going for testing  |
Alok Kumar Singh |
| |
|
Re: Integration Testing |
Reply # 7 |
integration testing:-all under control condition of
application's both the function works correctly or not to
check that functionality is called integration testing.
thank you.  |
Sim |
| |
|
Re: Integration Testing |
Reply # 8 |
it is a testing in which units will be tested,these units
will be combined or integrated to form complete system  |
Ch.lakshmi |
| |
|
Re: Integration Testing |
Reply # 9 |
As the name suggests 'Integration' means intigrating
somthing, can be any object/product/software module and
after integrating it, check what's it's functionality,
performance and all.
Usually, integration testing is done after UNIT Testing and
before SYSTEM Testing starts in the Software Development
Life Cycle.
Integration Testing can be done in both of the ways.
By using Black Box Testing Statergy or by using White Box
Testing Statergy.  |
Bajrang Badaik |
| |
|
Re: Integration Testing |
Reply # 10 |
Testing the interface/relationship/connectivity/bridge
between the modules (or) between the features.
it done mainly on two approaches..
bing bang approach
incremental approach
a) Top downApproach
b) Bottom Up Approach.  |
Koteswar_123@yahoo.co.in |
| |
|
Re: Integration Testing |
Reply # 11 |
We think Integration Testing should validate if systems
exchange data as in business process definitions.
A full integration test will consider all systems required
for a business process end-to-end. However it focuses on the
interoperability of the systems and does not consider
organizational issues.  |
Cridon |
| |
|
Re: Integration Testing |
Reply # 12 |
Visit Below link to Know Answer
http://www.fullinterview.com
 |
Kris |
| |
|
Re: Integration Testing |
Reply # 13 |
Giving an error report whether
a) critical
b) trivial
c) normal  |
Divya |
| |
|
Re: Integration Testing |
Reply # 14 |
it is the testing done once we get all the modules, before
this we do functional testing in this we test each and every
component works or not after this we go for integration
testing where the components are tested integrating them,
ex: in gmail we have many features like inbox, compose mail,
sent items,,,,,,, so the functionsl testin is testing each
and every feature but in intg tes.. first the mail is
composed and sent and then it is checked in sent items so
here we integrating two features  |
Sam |
| |
|
Re: Integration Testing |
Reply # 15 |
integration testin is a interface of software .
 |
Ravi |
| |
|
Re: Integration Testing |
Reply # 16 |
Upon completion of unit testing,integration testing
begins.Integration testing is black box testing.The purpose
of integration testing is to ensure distinct component of
application still work in accordance to customer
requirements.Testing cases are developed with the express
purpose of exercising the interfaces between the
components.This activity is carried out by the testing
team.Integration testing is considered complete,when actual
results and expected results are either in line or
differences are expandable/acceptable based on client input.  |
G.penchala Reddy |
| |
|
Re: Integration Testing |
Reply # 17 |
As the name suggests 'Integration' means integrating
something, can be any object/product/software module and
after integrating it, check what's it's functionality,
performance & what i am get the answer of my Integration.
 |
Sanjay |
| |
|
Re: Integration Testing |
Reply # 18 |
It is kind of testing by combining modules and checking for
the data flow between them or Sequence of functional
testing is called Integration testing  |
Vimal Kumar |
| |
|
Re: Integration Testing |
Reply # 19 |
Integration testing is a level of testing performed to
expose
defects in the interfaces and in the interactions between
integrated components or systems.
There may be more than one level of integration testing :-
1) Component integration testing
2) System integration testing
Within incremental integration testing a range of
possibilities exist, partly depending on the system
architecture:-
1) Top-down integration testing
2) Bottom-up integration testing
3) Functional incremental integration testing  |
Sitam Jana |
| |
| |
| |
| |
| |