| | 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
Working towards Effective Integration Testing

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



Joined: 31 Aug 2007
Posts: 13

PostPosted: Mon Sep 10, 2007 12:42 pm    Post subject: Working towards Effective Integration Testing Reply with quote

What factors that affect Software Integration and hence Integration Testing..?
Back to top
View user's profile Send private message
stone



Joined: 29 Aug 2007
Posts: 16

PostPosted: Mon Sep 10, 2007 12:43 pm    Post subject: Working towards Effective Integration Testing... Reply with quote

There are various factors that affect Software Integration and hence Integration Testing:

1) Software Configuration Management: Since Integration Testing focuses on Integration of components and components can be built by different developers and even different development teams, it is important the right version of components are tested. This may sound very basic, but the biggest problem faced in n-tier development is integrating the right version of components. Integration testing may run through several iterations and to fix bugs components may undergo changes. Hence it is important that a good Software Configuration Management (SCM) policy is in place. We should be able to track the components and their versions. So each time we integrate the application components we know exactly what versions go into the build process.

2) Automate Build Process where Necessary: A Lot of errors occur because the wrong version of components were sent for the build or there are missing components. If possible write a script to integrate and deploy the components this helps reduce manual errors.

3) Document: Document the Integration process/build process to help eliminate the errors of omission or oversight. It is possible that the person responsible for integrating the components forgets to run a required script and the Integration Testing will not yield correct results.

4) Defect Tracking: Integration Testing will lose its edge if the defects are not tracked correctly. Each defect should be documented and tracked. Information should be captured as to how the defect was fixed. This is valuable information. It can help in future integration and deployment processes.
Back to top
View user's profile Send private message
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 | |