About (not) testing private methods
Gregory Brown (author of Ruby Best Practices - available for free as PDF) discusses the issues around tests involving private methods. The gist of it is that private methods should only encapsulate auxiliary functionality that is so trivial that it doesn’t need to be tested. Any more complex code found in private methods can be regarded as code smell indicating that the method should be exposed as public or that there are more serious underlying design flaws.
