uninitialized constant Spec (NameError)
Reported by Aaron Wheeler | March 5th, 2008 @ 05:04 PM
I've got a fresh app generated by a nightly of Merb 0.9.1 (d06148fec38a07aa50ac09e7ec12f71ca0f7f2e8).
I've tried rolling back to tag v0.9.0, but when running my tests I get the RubiGen not found error.
I'm using DataMapper and have tried using both PostgreSQL and SQLite3.
The first problem is that Spec isn't automatically included; I have to manually include it in my spec_helper.rb.
The second problem is that as long as my DataMapper models don't contain any properties, the tests pass. Once I create properties for the models, however, the tests will pass the first time I run them on an empty database, but will fail every time thereafter.
The problem appears to be that my proper models aren't being included, but rather inferred from the database.
Here is a Pastie of my setup and the errors I'm getting:
Anyone else seen this problem in their Merb app?
Comments and changes to this ticket
-
Aaron Wheeler March 6th, 2008 @ 04:11 PM
This ticket contains two issues.
- rspec is not required unless rake tasks are used to run the specs. Does it make sense to include this as a requirement for when specs by hand? (e.g. ruby spec/models/blog.rb )
- DataMapper model corruption. I've created a separate ticket dealing with this issue.
-
Ezra Zygmuntowicz March 25th, 2008 @ 02:32 AM
- → State changed from “new” to “resolved”
this is resolved except for the mysterious missing dm properties. im closing this ticket as there are other dm tickets for this issue.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
James Herdman