Well, I think it all depends on the scenario - but in a lot of cases it should absolutely be considered a code-smell.<br><br>Stefan<br><br><div><span class="gmail_quote">2008/1/9, Kerry Buckley <<a href="mailto:kerry@kerrybuckley.com">
kerry@kerrybuckley.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Jan 9, 2008 10:01 AM, Stefan Magnus Landrø <<a href="mailto:stefan.landro@gmail.com">
stefan.landro@gmail.com</a>> wrote:<br>> I totally agree with you, David!<br>><br>> For quite a while I was testing all my methods (even had to declare them<br>> protected/package scope in java!), but I realized that I was getting into a
<br>> lot of trouble. Now I've shifted to testing functionality in stead of<br>> methods.<br>><br>> Now, sometimes you might end up having small methods (typically a result of<br>> refactoring) that are being used by several clients. In that case you should
<br>> start testing those methods, since they actually represent real business<br>> logic.<br><br>I wonder whether that is a smell indicating that the functionality in<br>those methods really belongs in its own class?
<br><br>Kerry<br>--<br><a href="http://www.kerrybuckley.com/">http://www.kerrybuckley.com/</a><br>_______________________________________________<br>rspec-users mailing list<br><a href="mailto:rspec-users@rubyforge.org">rspec-users@rubyforge.org
</a><br><a href="http://rubyforge.org/mailman/listinfo/rspec-users">http://rubyforge.org/mailman/listinfo/rspec-users</a><br></blockquote></div><br><br clear="all"><br>-- <br>Bekk Open Source<br><a href="http://boss.bekk.no">
http://boss.bekk.no</a>