<?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: Testing Cocoa Controllers with OCMock</title>
	<atom:link href="http://erik.doernenburg.com/2008/07/testing-cocoa-controllers-with-ocmock/feed/" rel="self" type="application/rss+xml" />
	<link>http://erik.doernenburg.com/2008/07/testing-cocoa-controllers-with-ocmock/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Mon, 02 Jan 2012 19:53:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Using OCMock with Mac OS X Lion, Xcode 4, to Mock and Unit Test Cocoa Desktop Apps &#171; Procbits</title>
		<link>http://erik.doernenburg.com/2008/07/testing-cocoa-controllers-with-ocmock/comment-page-1/#comment-10595</link>
		<dc:creator>Using OCMock with Mac OS X Lion, Xcode 4, to Mock and Unit Test Cocoa Desktop Apps &#171; Procbits</dc:creator>
		<pubDate>Tue, 29 Nov 2011 17:07:30 +0000</pubDate>
		<guid isPermaLink="false">http://erik.doernenburg.com/?p=44#comment-10595</guid>
		<description>[...] Testing Cocoa Controllers with OCMock [...]</description>
		<content:encoded><![CDATA[<p>[...] Testing Cocoa Controllers with OCMock [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mobile Testing</title>
		<link>http://erik.doernenburg.com/2008/07/testing-cocoa-controllers-with-ocmock/comment-page-1/#comment-10311</link>
		<dc:creator>Mobile Testing</dc:creator>
		<pubDate>Mon, 24 Oct 2011 13:09:31 +0000</pubDate>
		<guid isPermaLink="false">http://erik.doernenburg.com/?p=44#comment-10311</guid>
		<description>Thank you for providing this detailed explanation regarding testing of the user interface and for the quick summary at the end. This post was very helpful to me, as I&#039;m sure it was for a number of other people struggling with UI testing. Using dynamic mock objects definitely makes testing easier!</description>
		<content:encoded><![CDATA[<p>Thank you for providing this detailed explanation regarding testing of the user interface and for the quick summary at the end. This post was very helpful to me, as I&#8217;m sure it was for a number of other people struggling with UI testing. Using dynamic mock objects definitely makes testing easier!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Testing iPhone View Controllers &#124; The Carbon Emitter</title>
		<link>http://erik.doernenburg.com/2008/07/testing-cocoa-controllers-with-ocmock/comment-page-1/#comment-9350</link>
		<dc:creator>Testing iPhone View Controllers &#124; The Carbon Emitter</dc:creator>
		<pubDate>Sat, 11 Jun 2011 00:53:26 +0000</pubDate>
		<guid isPermaLink="false">http://erik.doernenburg.com/?p=44#comment-9350</guid>
		<description>[...] I have been writing tests around my iPhone apps&#8217; view controllers in order to follow the same TDD practices we use in other environments. Writing tests first has changed the way I structure my code in a couple of ways which I think offer immediate and emergent benefits for my applications. Most of an iPhone application&#8217;s business logic is implemented in its view controllers. Testing those controllers is therefore a priority if I want to have a well tested application. Below are some examples of the sort of tests I have written for my view controllers using GTM, Hamcrest, and OCMock (our iPhone Unit Testing Toolkit). Hopefully this can serve as a starting point for the tests you could be writing for your own projects.  Testing Interface Builder Bindings Broken nib bindings appear to be a common cause of application bugs during development. It is certainly easy enough to accidentally break or forget to create a binding while editing a nib file so let&#8217;s write some simple tests to assert that our actions and outlets are actually connected to objects in a nib file. These are really tests of the nib file itself. If the goal was to test the view controller&#8217;s use of these bound view objects I would replace the views with mock objects which could verify the controller&#8217;s behavior. (Erik Dörnenburg has provided a nice example of doing just that: Testing Cocoa Controllers with OCMock) [...]</description>
		<content:encoded><![CDATA[<p>[...] I have been writing tests around my iPhone apps&#8217; view controllers in order to follow the same TDD practices we use in other environments. Writing tests first has changed the way I structure my code in a couple of ways which I think offer immediate and emergent benefits for my applications. Most of an iPhone application&#8217;s business logic is implemented in its view controllers. Testing those controllers is therefore a priority if I want to have a well tested application. Below are some examples of the sort of tests I have written for my view controllers using GTM, Hamcrest, and OCMock (our iPhone Unit Testing Toolkit). Hopefully this can serve as a starting point for the tests you could be writing for your own projects.  Testing Interface Builder Bindings Broken nib bindings appear to be a common cause of application bugs during development. It is certainly easy enough to accidentally break or forget to create a binding while editing a nib file so let&#8217;s write some simple tests to assert that our actions and outlets are actually connected to objects in a nib file. These are really tests of the nib file itself. If the goal was to test the view controller&#8217;s use of these bound view objects I would replace the views with mock objects which could verify the controller&#8217;s behavior. (Erik Dörnenburg has provided a nice example of doing just that: Testing Cocoa Controllers with OCMock) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Testing View Controllers &#171; Carbon Five Community</title>
		<link>http://erik.doernenburg.com/2008/07/testing-cocoa-controllers-with-ocmock/comment-page-1/#comment-6484</link>
		<dc:creator>Testing View Controllers &#171; Carbon Five Community</dc:creator>
		<pubDate>Wed, 10 Mar 2010 18:01:16 +0000</pubDate>
		<guid isPermaLink="false">http://erik.doernenburg.com/?p=44#comment-6484</guid>
		<description>[...] the controller&#8217;s behavior. (Erik Dörnenburg has provided a nice example of doing just that: Testing Cocoa Controllers with OCMock) - &#040;void&#041; testViewBinding &#123; TestableSimpleViewController *viewController = [...]</description>
		<content:encoded><![CDATA[<p>[...] the controller&#8217;s behavior. (Erik Dörnenburg has provided a nice example of doing just that: Testing Cocoa Controllers with OCMock) &#8211; &#40;void&#41; testViewBinding &#123; TestableSimpleViewController *viewController = [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

