<?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: How to unit-test code that interacts with a database</title>
	<atom:link href="http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/</link>
	<description>Stay curious!</description>
	<lastBuildDate>Thu, 09 Feb 2012 20:41:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: John Battista</title>
		<link>http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-18456</link>
		<dc:creator>John Battista</dc:creator>
		<pubDate>Wed, 30 Jun 2010 18:03:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-18456</guid>
		<description>Very interesting read. I just felt the need to point out that mock objects are necessarily the level of evil you make them out to be, especially if you have physical inputs to your system.

The difficulty in causes real physical interactions / conditions to control the output of sensors that is used by other objects requires construction of further physical interaction equipment with sensors ect. 

In cases like that trying to create the physical interactions instead of mocking up the data streams is equivalent to trying to mock out a database instead of using a real one. You create a massive work burden on yourself that cannot really be fulfilled and used to test a full range of conditions. With mocks in a physical interaction system you can send in the full range of possible data in a fraction of the time at a fraction of the cost.

Just like any other tool its not good or bad, but it needs to be applied properly!</description>
		<content:encoded><![CDATA[<p>Very interesting read. I just felt the need to point out that mock objects are necessarily the level of evil you make them out to be, especially if you have physical inputs to your system.</p>
<p>The difficulty in causes real physical interactions / conditions to control the output of sensors that is used by other objects requires construction of further physical interaction equipment with sensors ect. </p>
<p>In cases like that trying to create the physical interactions instead of mocking up the data streams is equivalent to trying to mock out a database instead of using a real one. You create a massive work burden on yourself that cannot really be fulfilled and used to test a full range of conditions. With mocks in a physical interaction system you can send in the full range of possible data in a fraction of the time at a fraction of the cost.</p>
<p>Just like any other tool its not good or bad, but it needs to be applied properly!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick</title>
		<link>http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-17510</link>
		<dc:creator>Rick</dc:creator>
		<pubDate>Tue, 29 Dec 2009 00:23:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-17510</guid>
		<description>Guys,
is there any tool to do unit test on MySQL?
Thx.</description>
		<content:encoded><![CDATA[<p>Guys,<br />
is there any tool to do unit test on MySQL?<br />
Thx.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank</title>
		<link>http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-17475</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Wed, 23 Dec 2009 23:30:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-17475</guid>
		<description>One approach we have used successfully was to embed the mysql server into our C++ test executables. At least for the relatively small database that the project included this worked reasonably well.
No modifications to the database access layer were necessary and creating a blank database was just a matter of copying some small files into a temporary directory. You loose the ability to easily debug the content of the database, but with some dump-tools this was not a big problem.</description>
		<content:encoded><![CDATA[<p>One approach we have used successfully was to embed the mysql server into our C++ test executables. At least for the relatively small database that the project included this worked reasonably well.<br />
No modifications to the database access layer were necessary and creating a blank database was just a matter of copying some small files into a temporary directory. You loose the ability to easily debug the content of the database, but with some dump-tools this was not a big problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Applications et bases de données, comment tester ? &#171; Choses à faire</title>
		<link>http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-17452</link>
		<dc:creator>Applications et bases de données, comment tester ? &#171; Choses à faire</dc:creator>
		<pubDate>Thu, 17 Dec 2009 09:47:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-17452</guid>
		<description>[...] les Mocks peuvent ne pas être appropriés pour les tests d&#8217;accès à la base, certains les déconseillent même vivement.Les avantages sont une vitesse d&#8217;exécution bien supérieure, en plus de pouvoir tester [...]</description>
		<content:encoded><![CDATA[<p>[...] les Mocks peuvent ne pas être appropriés pour les tests d&#8217;accès à la base, certains les déconseillent même vivement.Les avantages sont une vitesse d&#8217;exécution bien supérieure, en plus de pouvoir tester [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nathanr</title>
		<link>http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-16651</link>
		<dc:creator>nathanr</dc:creator>
		<pubDate>Fri, 10 Jul 2009 11:09:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.xaprb.com/blog/2008/08/19/how-to-unit-test-code-that-interacts-with-a-database/#comment-16651</guid>
		<description>justinb is spot on unit tests responsibility is to test the actual implementation of a class. Outside/external components that are outside of the control or scope of a codebase is something that gets addressed with integration tests. Were the focus is to exercise interaction between different components whether they are internal or external to a codebase.</description>
		<content:encoded><![CDATA[<p>justinb is spot on unit tests responsibility is to test the actual implementation of a class. Outside/external components that are outside of the control or scope of a codebase is something that gets addressed with integration tests. Were the focus is to exercise interaction between different components whether they are internal or external to a codebase.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

