How is normal testing differ from Integration testing?
Ans:First, integration project architectures are
message-based, not code-based, and the failure points are generally in
the messages, not in the code as they would be in an application
development project.
This kind of testing requires stubs more than a application testing does
Testing in an integration project needs to focus on the messaging. Both
the business and technical team members need to think about message
flows and logic, and the tools they use should be designed to support
messages.
Message testing tools, on the other hand, are designed to test at the message level and to pinpoint message problems.
Organizationally, teams need to think not just about their code, but
how it affects both input and output components. Most application
development teams don't have the vision or the technology to validate
their systems operation in the overall enterprise. An integration
project may also include many different technologies, such as XML, MQ,
TCP/IP and others. Integration teams need tools that work with many
technologies so they can validate the technology handoffs, as well as
the business logic.
Finally -- and most importantly -- it is almost impossible in a
large integration project to orchestrate an end-to-end test with
application test tools. What integration projects need is the ability
to test early in development. They need to unit test, and component
test, pieces of the logic before all the pieces are available.
------------- MBA Examination papers
|