<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Virtuous Code - Latest Comments in Testing Private Methods</title><link>http://virtuouscode.disqus.com/</link><description></description><atom:link href="https://virtuouscode.disqus.com/testing_private_methods/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 20 Jan 2011 09:56:31 -0000</lastBuildDate><item><title>Re: Testing Private Methods</title><link>http://devblog.avdi.org/2008/10/21/testing-private-methods/#comment-131813640</link><description>&lt;p&gt;I believe you are confusing two two job descriptions. Some organizations have professional testers whose job, indeed, is to find bugs. Typically they are not the ones writing unit tests. They are usually writing much higher-level full-system test scripts. When I, as a developer, write unit tests I'm doing it to drive out a good design. The fact that the resulting test suite is good at catching regressions is a handy side-effect.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Avdi Grimm</dc:creator><pubDate>Thu, 20 Jan 2011 09:56:31 -0000</pubDate></item><item><title>Re: Testing Private Methods</title><link>http://devblog.avdi.org/2008/10/21/testing-private-methods/#comment-131393719</link><description>&lt;p&gt;Remember that the purpose of testing is to find bugs. There is no question of right or wrong but a question of whether testers are finding mistakes, deviations, and errors more effectively. There are many works covering the topic of software testing. I recommend the works of Cem Kaner.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ecjones2040</dc:creator><pubDate>Wed, 19 Jan 2011 12:37:20 -0000</pubDate></item><item><title>Re: Testing Private Methods</title><link>http://devblog.avdi.org/2008/10/21/testing-private-methods/#comment-4591771</link><description>&lt;p&gt;Nice writeup.  I agree with breaking out the code into separate classes here.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Craig Jolicoeur</dc:creator><pubDate>Tue, 23 Dec 2008 12:22:43 -0000</pubDate></item><item><title>Re: Testing Private Methods</title><link>http://devblog.avdi.org/2008/10/21/testing-private-methods/#comment-3252498</link><description>&lt;p&gt;Ruby doesn't really support the notion of free functions (it kind of fakes it, but in a way I prefer not to take advantage of in anything but quick one-off scripts).  It could be a class-level method, I suppose.  I still prefer the class approach, because then if you decide to mock the slugification out you're not mocking methods on the class under test.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Avdi Grimm</dc:creator><pubDate>Thu, 23 Oct 2008 11:36:17 -0000</pubDate></item><item><title>Re: Testing Private Methods</title><link>http://devblog.avdi.org/2008/10/21/testing-private-methods/#comment-3231014</link><description>&lt;p&gt;Or the `slugify` method could be turned into a function, since it isn't really relevant to the `BlogPost` instance.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Daniel Schierbeck</dc:creator><pubDate>Wed, 22 Oct 2008 11:38:58 -0000</pubDate></item><item><title>Re: Testing Private Methods</title><link>http://devblog.avdi.org/2008/10/21/testing-private-methods/#comment-3225166</link><description>&lt;p&gt;Couldn't agree more. I often hear questions about testing private methods and to me it makes no sense whatsoever. As you say: private methods are an implementation detail!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ben</dc:creator><pubDate>Wed, 22 Oct 2008 08:13:35 -0000</pubDate></item><item><title>Re: Testing Private Methods</title><link>http://devblog.avdi.org/2008/10/21/testing-private-methods/#comment-3224830</link><description>&lt;p&gt;I'm glad to have at least  provided a little bit inspiration for this blog post.  We totally see eye-to-eye on this matter.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bryanl</dc:creator><pubDate>Wed, 22 Oct 2008 07:32:37 -0000</pubDate></item></channel></rss>