<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: What is Integration Testing?</title>
	<atom:link href="http://www.dbuggr.com/abhaybharti/integration-testing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dbuggr.com/abhaybharti/integration-testing/</link>
	<description>Share Knowledge &#38; Be Rewarded</description>
	<lastBuildDate>Fri, 03 Feb 2012 23:13:48 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Kunal</title>
		<link>http://www.dbuggr.com/abhaybharti/integration-testing/comment-page-1/#comment-1014</link>
		<dc:creator>Kunal</dc:creator>
		<pubDate>Thu, 24 Dec 2009 11:15:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.dbuggr.com/abhaybharti/integration-testing/#comment-1014</guid>
		<description>Integration testing (sometimes called Integration and testing and abbreviated I&amp;T) is the phase of software testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing.

The purpose of Integration testing is to verify functional, performance and reliability requirements placed on major design items. These &quot;design items&quot;, i.e. assemblages (or groups of units), are exercised through their interfaces using Black box testing, success and error cases being simulated via appropriate parameter and data inputs.
The overall idea is a &quot;building block&quot; approach, in which verified assemblages are added to a verified base which is then used to support the Integration testing of further assemblages.
The different types of integration testing are Big Bang, Top Down, Bottom Up, and Back bone.</description>
		<content:encoded><![CDATA[<p>Integration testing (sometimes called Integration and testing and abbreviated I&amp;T) is the phase of software testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing.</p>
<p>The purpose of Integration testing is to verify functional, performance and reliability requirements placed on major design items. These &#8220;design items&#8221;, i.e. assemblages (or groups of units), are exercised through their interfaces using Black box testing, success and error cases being simulated via appropriate parameter and data inputs.<br />
The overall idea is a &#8220;building block&#8221; approach, in which verified assemblages are added to a verified base which is then used to support the Integration testing of further assemblages.<br />
The different types of integration testing are Big Bang, Top Down, Bottom Up, and Back bone.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
