<?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: AI Failure Story: Paying a Heavy Price for Test Strategy Errors	</title>
	<atom:link href="https://www.softwaretestingmagazine.com/knowledge/ai-failure-story-paying-a-heavy-price-for-test-strategy-errors/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.softwaretestingmagazine.com/knowledge/ai-failure-story-paying-a-heavy-price-for-test-strategy-errors/</link>
	<description></description>
	<lastBuildDate>Thu, 15 Nov 2018 17:17:47 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Durga		</title>
		<link>https://www.softwaretestingmagazine.com/knowledge/ai-failure-story-paying-a-heavy-price-for-test-strategy-errors/#comment-32478</link>

		<dc:creator><![CDATA[Durga]]></dc:creator>
		<pubDate>Thu, 11 Oct 2018 14:40:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwaretestingmagazine.com/?p=6621#comment-32478</guid>

					<description><![CDATA[Agile when done correctly requires a lot of planning.  You need a plan to reflect which features will be developed, you need a plan to reflect when unit testing, system testing, integration testing will be performed etc.  For example - Integration testing can be done once every sprint or one for a release or every other sprint.  You definitely need a strategy.  We used to write test cases that ultimately helped developers verify their code and fill any gaps.]]></description>
			<content:encoded><![CDATA[<p>Agile when done correctly requires a lot of planning.  You need a plan to reflect which features will be developed, you need a plan to reflect when unit testing, system testing, integration testing will be performed etc.  For example &#8211; Integration testing can be done once every sprint or one for a release or every other sprint.  You definitely need a strategy.  We used to write test cases that ultimately helped developers verify their code and fill any gaps.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Samy Ingals		</title>
		<link>https://www.softwaretestingmagazine.com/knowledge/ai-failure-story-paying-a-heavy-price-for-test-strategy-errors/#comment-32422</link>

		<dc:creator><![CDATA[Samy Ingals]]></dc:creator>
		<pubDate>Thu, 20 Sep 2018 11:38:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.softwaretestingmagazine.com/?p=6621#comment-32422</guid>

					<description><![CDATA[Unfortunately, with all this Agile crap going on in software development and software testing currently, people believe that it is not worth to think and develop a test strategy before delivering code!!!!]]></description>
			<content:encoded><![CDATA[<p>Unfortunately, with all this Agile crap going on in software development and software testing currently, people believe that it is not worth to think and develop a test strategy before delivering code!!!!</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
