<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>« Simple and Pragmatic Thoughts » &#187; TDD</title>
	<atom:link href="http://isagoksu.com/categories/development/agile-development/test-driven-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://isagoksu.com</link>
	<description>Nobody can be perfect, but you can think better, design better, and always use baby steps!</description>
	<lastBuildDate>Tue, 16 Mar 2010 03:39:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Making Code More Testable &#8211; Breaking Static Dependencies</title>
		<link>http://isagoksu.com/2009/development/agile-development/test-driven-development/making-code-more-testable-breaking-static-dependencies/</link>
		<comments>http://isagoksu.com/2009/development/agile-development/test-driven-development/making-code-more-testable-breaking-static-dependencies/#comments</comments>
		<pubDate>Mon, 31 Aug 2009 08:07:31 +0000</pubDate>
		<dc:creator>Isa Goksu</dc:creator>
				<category><![CDATA[TDD]]></category>
		<category><![CDATA[break]]></category>
		<category><![CDATA[constructor]]></category>
		<category><![CDATA[delegate]]></category>
		<category><![CDATA[dependency]]></category>
		<category><![CDATA[mockito]]></category>
		<category><![CDATA[static]]></category>

		<guid isPermaLink="false">http://isagoksu.com/?p=531</guid>
		<description><![CDATA[<p>Hi guys, it&#8217;s been a while that I haven&#8217;t posted anything. I was thinking writing all those technical things sometimes is not enough for the reader to visualize the concept. So I came up with a screencast this time. I&#8217;ll try to create these screencasts once a week and will cover different topics. This series will contain <strong>Making Code More Testable</strong> talks only. For other topics, I&#8217;ll create different series. Anyways, let&#8217;s get back to the overview :)</p>]]></description>
			<content:encoded><![CDATA[<p>Hi guys, it&#8217;s been a while that I haven&#8217;t posted anything. I was thinking writing all those technical things sometimes is not enough for the reader to visualize the concept. So I came up with a screencast this time. I&#8217;ll try to create these screencasts once a week and will cover different topics. This series will contain <strong>Making Code More Testable</strong> talks only. For other topics, I&#8217;ll create different series. Anyways, let&#8217;s get back to the overview :)</p>]]></content:encoded>
			<wfw:commentRss>http://isagoksu.com/2009/development/agile-development/test-driven-development/making-code-more-testable-breaking-static-dependencies/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
<enclosure url="http://isagoksu.com/wp-content/uploads/screencasts/tdd/01.mov" length="37775037" type="video/quicktime" />
		</item>
		<item>
		<title>Using JUnit DataPoints and Theories</title>
		<link>http://isagoksu.com/2009/development/agile-development/test-driven-development/using-junit-datapoints-and-theories/</link>
		<comments>http://isagoksu.com/2009/development/agile-development/test-driven-development/using-junit-datapoints-and-theories/#comments</comments>
		<pubDate>Tue, 14 Jul 2009 06:58:38 +0000</pubDate>
		<dc:creator>Isa Goksu</dc:creator>
				<category><![CDATA[TDD]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[driven]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[junit]]></category>
		<category><![CDATA[test]]></category>

		<guid isPermaLink="false">http://isagoksu.com/2009/general/using-junit-datapoints-and-theories/</guid>
		<description><![CDATA[I'm not going to implement the best code ever, just to show the usage of @DataPoints, assume that our implementation is like below: public class RockPaperScissorEvaluator { public static enum Hand { ROCK, PAPER, SCISSOR } public Integer evaluate(Hand side1, Hand side2) { if (side1.equals(Hand.ROCK) &#38;&#38; !side2.equals(Hand.ROCK)) { return (side2.equals(Hand.SCISSOR)) ?]]></description>
			<content:encoded><![CDATA[<p>Today I was digging something for one of my custom projects in <a href="http://junit.org" title="JUnit?s Home Page" target="_blank">JUnit</a>&#8217;s package and I came across with very nice feature. I think it&#8217;s going to make much more sense after my first <a href="http://isagoksu.com/2009/development/agile-development/test-driven-development/using-junit-parameterized-annotation/" title="JUnit?s Parameterized Annotation" target="_blank">article</a> about <a href="http://junit.org" title="JUnit?s Home Page" target="_blank">JUnit</a>&#8217;s <strong>@Parameterized</strong> annotation.</p>]]></content:encoded>
			<wfw:commentRss>http://isagoksu.com/2009/development/agile-development/test-driven-development/using-junit-datapoints-and-theories/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Using JUnit Parameterized Annotation</title>
		<link>http://isagoksu.com/2009/development/agile-development/test-driven-development/using-junit-parameterized-annotation/</link>
		<comments>http://isagoksu.com/2009/development/agile-development/test-driven-development/using-junit-parameterized-annotation/#comments</comments>
		<pubDate>Fri, 12 Jun 2009 02:27:10 +0000</pubDate>
		<dc:creator>Isa Goksu</dc:creator>
				<category><![CDATA[TDD]]></category>
		<category><![CDATA[annotation]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[junit]]></category>
		<category><![CDATA[parameterized]]></category>

		<guid isPermaLink="false">http://isagoksu.com/?p=362</guid>
		<description><![CDATA[} @Parameterized.Parameters public static Collection primeNumbers() { return Arrays.asList(new Object { { 2, true }, { 6, false }, { 19, true }, { 22, false } });]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s been a while since my last post. I thought that maybe it&#8217;s time to post some new stuff :) OK, here it is:</p>]]></content:encoded>
			<wfw:commentRss>http://isagoksu.com/2009/development/agile-development/test-driven-development/using-junit-parameterized-annotation/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Tips For Better Tests &#8211; Part 2</title>
		<link>http://isagoksu.com/2009/development/agile-development/test-driven-development/tips-for-better-tests-part-2/</link>
		<comments>http://isagoksu.com/2009/development/agile-development/test-driven-development/tips-for-better-tests-part-2/#comments</comments>
		<pubDate>Sun, 03 May 2009 05:34:49 +0000</pubDate>
		<dc:creator>Isa Goksu</dc:creator>
				<category><![CDATA[TDD]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[driven]]></category>
		<category><![CDATA[ted]]></category>
		<category><![CDATA[test]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://isagoksu.com/?p=366</guid>
		<description><![CDATA[In the last post, I tried to roughly touch Unit Tests and what/how many and when to test our Units. I'll try to cover why we test, why we automate our tests, life-cycle of agile testing process, what kind of tests are available in an agile environment, open sources tools available in the market, etc.]]></description>
			<content:encoded><![CDATA[<p>In the last post, I tried to roughly touch <em>Unit Tests</em> and what/how many and when to test our <em>Units</em>. For more information about that topic, please go back to <a href="http://isagoksu.com/2009/development/agile-development/test-driven-development/tips-for-better-tests-part-1/" title="Tips for Better Tests Part I">first article</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://isagoksu.com/2009/development/agile-development/test-driven-development/tips-for-better-tests-part-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tips For Better Tests &#8211; Part 1</title>
		<link>http://isagoksu.com/2009/development/agile-development/test-driven-development/tips-for-better-tests-part-1/</link>
		<comments>http://isagoksu.com/2009/development/agile-development/test-driven-development/tips-for-better-tests-part-1/#comments</comments>
		<pubDate>Thu, 05 Feb 2009 10:41:20 +0000</pubDate>
		<dc:creator>Isa Goksu</dc:creator>
				<category><![CDATA[TDD]]></category>
		<category><![CDATA[Development]]></category>
		<category><![CDATA[driven]]></category>
		<category><![CDATA[ted]]></category>
		<category><![CDATA[test]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[unit]]></category>

		<guid isPermaLink="false">http://isagoksu.com/?p=179</guid>
		<description><![CDATA[Slow forms, Time critical applications When not to test: For Private methods if it is just refactoring or maintance When unit tests start to test integrational units, please don't do this, don't get lost in tests!]]></description>
			<content:encoded><![CDATA[<p>I remember my generation and how we were having trouble with understanding Test Driven Development (Design). First it came like TFD (Test First Development) which you were writing your tests before going into any code. But then this doesn&#8217;t fit into practical world. And TDD came into our world. Right now in turns into TED (Test Enhanced Design). Hehe.. Anyway, I just want to share my experience with all these. If you&#8217;re just starting this technique, you might find it a little bit hard to identify what/how many and when you should use this technique. And maybe more interesting, what is all about? what is unit test, what is integration test, what is functional test, what is acceptance test, etc.</p>]]></content:encoded>
			<wfw:commentRss>http://isagoksu.com/2009/development/agile-development/test-driven-development/tips-for-better-tests-part-1/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

