Good point with... test "the truth"... I'll have to dig a bit more because my test didn't seem to be replacing anything in the current class.
Thanks On Thu, Dec 17, 2009 at 10:57 PM, Michael Koziarski <[email protected]> wrote: >> What's the purpose for "test" working this way? > > It should only be doing this if the method you're defining would be > *replacing* another test, it shouldn't matter if you have test with > the same name in different classes. The warning's saved me a few > times before, but it's possible that there's a bug that's causing the > behaviour that you're seeing. If you can reproduce it in a new app we > could have a bug, but I don't think that's too likely given every > newly generated unit test does: > > test "the truth" do > assert true > end > > > > > > -- > Cheers > > Koz > > -- > > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-core?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
