Hi, We have a project with a db table ''test'' and a corresponding model Test. When we run rake to invoke our tests, rake fails with the following error: /usr/lib/ruby/1.8/test/unit/assertionfailederror.rb:5: Test is not a module (TypeError) We believe this is caused by some namespace conflict between our model named Test and rake''s own internals. If we rename our Test class, this problem disappears; however, Test really is the right name in this circumstance. Can anyone suggest a possible method to resolve this issue? This can be recreated by taking any rails project and creating a model called Test. Attempting to run rake will yield the error above. -Kent -- Posted via http://www.ruby-forum.com/.
I get a same problem . -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Apparently Analagous Threads
- After Rails 2.3.2 upgrade: superclass mismatch for class TestCase (TypeError)
- AIX: TypeError: unsupported operand type(s) for +: '_hashlib.HASH' and 'str'
- fixture problem, TypeError: nil is not a symbol
- TypeError
- superclass mismatch for class OrderedOptions (TypeError)