| | Book ShopNew | Testing Tools | Testing Books | Testing Directory | Testing JobsNew | Testing CertificationsNew | |
testingsense.com
A forum to discuss Software Testing
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Software Testing Jobs
Only Software Testing Jobs
And Nothing Else
How is integration testing different from Normal testing

 
Post new topic   Reply to topic    testingsense.com Forum Index -> Integration testing
View previous topic :: View next topic  
Author Message
vigmanis
Site Admin


Joined: 01 Jan 1970
Posts: 65

PostPosted: Fri Nov 10, 2006 6:03 am    Post subject: How is integration testing different from Normal testing Reply with quote

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.
Back to top
View user's profile Send private message Send e-mail
DELETED
Guest





PostPosted: Wed Jan 03, 2007 3:13 am    Post subject: Reply with quote

DELETED
Back to top
DELETED
Guest





PostPosted: Wed Jan 03, 2007 9:58 pm    Post subject: Reply with quote

DELETED
Back to top
DELETED
Guest





PostPosted: Thu Jan 04, 2007 1:47 am    Post subject: Reply with quote

DELETED
Back to top
DELETED
Guest





PostPosted: Thu Jan 04, 2007 5:44 pm    Post subject: Reply with quote

DELETED
Back to top
DELETED
Guest





PostPosted: Thu Jan 04, 2007 9:31 pm    Post subject: Reply with quote

DELETED
Back to top
DELETED
Guest





PostPosted: Fri Jan 05, 2007 1:07 am    Post subject: Reply with quote

DELETED
Back to top
Display posts from previous:   
Post new topic   Reply to topic    testingsense.com Forum Index -> Integration testing All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group
| | Book ShopNew | Testing Tools | Testing Books | Testing Directory | Testing JobsNew | Testing CertificationsNew | |