* Posting on behalf of James Mead ([EMAIL PROTECTED]) *
Sounds interesting. I've been doing my own monkey-patching recently (http://mocha.rubyforge.org/classes/MultipleSetupAndTeardown.html) and have noticed a couple of other people (http://www.agilewebdevelopment.com/plugins/testcase_setup_and_teardown_with_blocks and http://mabs29.googlecode.com/svn/trunk/plugins/active_test/lib/active_test/base.rb) doing similar things. It would be really good to get support for multiple setup/teardown methods into the Test::Unit library. James. On 8/19/06, Nathaniel Talbott <[EMAIL PROTECTED]> wrote:
On 8/18/06, Keith Morrison <[EMAIL PROTECTED]> wrote: > You could define a fake test, but then the test and assertion count will > be off. A simple: def default_test end In your abstract test case will prevent the failure, and while you will see an extra test, there will be no assertion inflation. I know that the default_test is pretty much universally hated (Ryan Davis has a colorfully named test method in one of his base classes to prevent it from failing) and I agree that it is/was a bad idea. I'm working on something that I'm hoping will greatly improve the ability for frameworks like Rails to do "frameworky stuff" for testing without completely monkey-patching the testing framework. More details when I have something concrete to show. HTH, -- Nathaniel Talbott <:((>< _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
_______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
