<?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: The automated testing triangle</title>
	<atom:link href="http://jonkruger.com/blog/2010/02/08/the-automated-testing-triangle/feed/" rel="self" type="application/rss+xml" />
	<link>http://jonkruger.com/blog/2010/02/08/the-automated-testing-triangle/</link>
	<description></description>
	<pubDate>Fri, 18 May 2012 01:18:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Confluence: New Product Development</title>
		<link>http://jonkruger.com/blog/2010/02/08/the-automated-testing-triangle/comment-page-1/#comment-5875</link>
		<dc:creator>Confluence: New Product Development</dc:creator>
		<pubDate>Thu, 22 Mar 2012 15:46:09 +0000</pubDate>
		<guid isPermaLink="false">http://jonkruger.com/blog/?p=453#comment-5875</guid>
		<description>&lt;strong&gt;Nature Jobs Automation improvements...&lt;/strong&gt;

Introduction   Problem Currently as it stands there are roughly 177 Cucumber feature tests that are run for each build.......</description>
		<content:encoded><![CDATA[<p><strong>Nature Jobs Automation improvements&#8230;</strong></p>
<p>Introduction   Problem Currently as it stands there are roughly 177 Cucumber feature tests that are run for each build&#8230;&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://jonkruger.com/blog/2010/02/08/the-automated-testing-triangle/comment-page-1/#comment-5535</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Wed, 02 Nov 2011 16:42:20 +0000</pubDate>
		<guid isPermaLink="false">http://jonkruger.com/blog/?p=453#comment-5535</guid>
		<description>"If you’ve ever worked on a project that had loads of manual testing, then you can at least imagine how nice it would be to have automated tests that would test a majority of your application by clicking a button."

Through the cycle:
TDD for unit tests i.e. NUnit + Rhino Mocks - Run these in CI Build
Integration tests with BDD with use the unit tested code i.e. SpecFlow - Run these in nighly build
Functional tests with automated UI test tool i.e. QTP - Run these in nightly build
Final functional tests done manually

That should cover it. Trick is to get everyone writing TDD as a standard, doing BDD as part of Stories in Agile and testers focused on automated testing tools.

Cheers, Tim</description>
		<content:encoded><![CDATA[<p>&#8220;If you’ve ever worked on a project that had loads of manual testing, then you can at least imagine how nice it would be to have automated tests that would test a majority of your application by clicking a button.&#8221;</p>
<p>Through the cycle:<br />
TDD for unit tests i.e. NUnit + Rhino Mocks - Run these in CI Build<br />
Integration tests with BDD with use the unit tested code i.e. SpecFlow - Run these in nighly build<br />
Functional tests with automated UI test tool i.e. QTP - Run these in nightly build<br />
Final functional tests done manually</p>
<p>That should cover it. Trick is to get everyone writing TDD as a standard, doing BDD as part of Stories in Agile and testers focused on automated testing tools.</p>
<p>Cheers, Tim</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Pocklington</title>
		<link>http://jonkruger.com/blog/2010/02/08/the-automated-testing-triangle/comment-page-1/#comment-5447</link>
		<dc:creator>Robert Pocklington</dc:creator>
		<pubDate>Wed, 09 Feb 2011 13:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://jonkruger.com/blog/?p=453#comment-5447</guid>
		<description>You make an excellent point re: QA and development, 'bridging the gap' so to speak.  If the project has a QA team, generally they are the ones doing full manual testing and if you can free up their time using automated tests (which they write with the B.A and the developers) then a) QA can invest in more thorough testing and b) you can execute the functional tests as part of a build process to give you an early warning - an automated QA team :)</description>
		<content:encoded><![CDATA[<p>You make an excellent point re: QA and development, &#8216;bridging the gap&#8217; so to speak.  If the project has a QA team, generally they are the ones doing full manual testing and if you can free up their time using automated tests (which they write with the B.A and the developers) then a) QA can invest in more thorough testing and b) you can execute the functional tests as part of a build process to give you an early warning - an automated QA team :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

